Creation of session bean

Hi all,
I am trying to create a DC webservice, while creating the stateless session bean in package, I am getting the error "Not able to create session bean".
How can I solve this issue?
Basically the problem is with the ejb-jar.xml.
Thanks
Vivek

Hi Sriram,
I have created another webservice locally and in that I am able to create the session bean. I am getting the problem only while creating the bean in the EJB module in DC.
Thanks
Vivek

Similar Messages

Issue with Webservice Creation using Session Beans.

Hi All,
I want to expose my Session beans as webservice.
I'm using Weblogic Application Server.
When I do the modeling using JDeveloper, I'm unable to convert the Session bean to webservice.
Any information on this is highly appreciable.
Thanks & Regards,
Kumar Madhavan.

I can't give you much of a walk through, as I have just started it myself, but I'm using a universal unique identifier to represent each client. Whenever a client posts data from a jsp or applet the uuid is also sent. I use POST to pass all my parameters. If the server hasen't received data in say 5 minutes from the client then it is assumed the client went offline. Its working for me so far.
COn

Is it possible to restrict the object creation for stateless session beans

Hi,
Is it possible to restrict/fix the ejb object creation for stateless session beans in application server?
For example, i want to configure the application server ( am using JBOSS ) to create maximum of 10 session bean objects. and if any requests for the stateless session bean come, as application server has created 10 objects, the requests should be blocked.
Thanks in advance,
nvseenu

You can keep a counter in the application code. A static var won't work, but an entity and a consistent id should. This version would affect performance, but it would be portable to other app servers.
// ConstrainedBean.java
package unq.ejb;
import javax.ejb.Stateless;
import javax.ejb.CreateException;
import javax.annotation.PostConstruct;
import javax.annotation.PreDestroy;
import javax.persistence.PersistenceContext;
import javax.persistence.EntityManager;
@Stateless
public class ConstrainedBean implements Constrained {
    final static int DEFAULT_COUNTERID = 1;
    @PersistenceContext EntityManager em;
    @PostConstruct
    protected void init() throws CreateException {
     ConstrainedBeanCounter counter =
         em.find(ConstrainedBeanCounter.class, DEFAULT_COUNTERID);
     if( counter == null ) {
         counter = new ConstrainedBeanCounter();
         counter.counterId = 1;
         counter.counterValue = 0;
         em.persist(counter);
     if( counter.atMaximum() ) {
         throw new CreateException("error attempting to create > 10 beans");
     else {
         counter.increment();
    @PreDestroy
    protected void destroy() {
     ConstrainedBeanCounter counter = em.find(ConstrainedBeanCounter.class,
                               DEFAULT_COUNTERID);
     counter.decrement();
    public void doSomething() { System.out.println("doSomething()"); }
// ConstrainedBeanCounter.java
package unq.ejb;
import javax.persistence.Entity;
import javax.persistence.Id;
@Entity
public class ConstrainedBeanCounter implements java.io.Serializable
    @Id public int counterId;
    public int counterValue = 0;
    public void increment() {
     counterValue++;
    public void decrement() {
     counterValue--;
    public boolean atMaximum() {
     return counterValue > 9;
}

Creating multiple stateful session beans from a java client. (EJB 3.0)

I'm having difficulties with the following:
To access the ShoppingCartBean, I have to put the following annotation in my standalone java client:
@EJB
private static ShoppingCartRemote shoppingCartBean;
The static must be there, thus only one ShoppingCartBean will exist within my java client. But as the ShoppingCartBean is a stateful session bean, I want to be able to get different beans of the same type.
What is the correct way to do this in EJB 3.0?

Great question. Because Home interfaces have been removed for the EJB 3.0 simplified
API, stateful session bean creation happens as a side-effect of injection. However, the
same is true of EJB 3.0 business interface lookups. The easiest way to create additional
stateful session beans is to lookup the same dependency that was declared via your
@EJB annotation.
E.g.,
// Assuming the declaring class is pkg1.ShoppingCartClient.java
InitialContext ic = new InitialContext();
ShoppingCartRemote scr1 = (ShoppingCartRemote)
ic.lookup("java:comp/env/pkg1.ShoppingCartClient/shoppingCartBean");
Note that the name relative to java:comp/env is the default associated with your
@EJB annotation since the name() attribute wasn't used. Alternatively, you
could have used :
@EJB(name="scb") private static ShoppingCartRemote shoppingCartBean;
InitialContext ic = new InitialContext();
ShoppingCartRemote scr1 = (ShoppingCartRemote) ic.lookup("java:comp/env/scb");
Yet another alternative is to declare the @EJB at the class-level. This just defines
the dependency without any injection, which is fine if you want to create a bunch of
them via lookup anyway.
@EJB(name="scb", beanInterface=ShoppingCartRemote.class)
public class .... {

Making AQ usage transactional across session beans, using mosly JMS syntax

I need to determine what I need to have in place in order for JMS/AQ messages to be "fully transactional".
I have a J2EE server application that will send JMS/AQ messages to a queue. I have a standalone application that reads messages from the queue, does some work, and then makes calls on multiple session beans (hosted in the original J2EE server application). Actually, it would likely be multiple calls to the same session bean method.
Once the standalone application reads a message from the queue, I need to ensure that if any action performed as a result of that message fails, that all the operations performed, including the removal of the message from the queue, are rolled back.
First of all, if I use an Oracle XA-compliant datasource, if one of the session bean calls fail, I can rollback the current transaction, but will this properly roll back any work that earlier session bean calls (made on the same transaction) did, even if they were successful (at the time)? Note that I have two JVMs, one running the J2EE application, and the other a standalone application reading from the queue.
Second, on committing or rolling back the message retrieval itself, I noticed from examples in the Oracle AQ Application Developer's Guide that if I create my QueueSessions with "AQDriverManager.createAQSession()", that I can pass a Connection object, and then later "commit" or "rollback", manually, perhaps if I got an EJBException from a session bean call.
However, I am trying to write my JMS/AQ code so that it uses as little of the direct AQ api as possible, staying with the standard JMS api. As a result, I'm using the JMS version of this, which is "QueueConnection.createQueueSession()". When I do this, however, it seems as if I lose control over the transaction.

Ok, I think I've answered some of this for myself, but I still have some concerns.
I see that the QueueSession object that I get back from "queueConnection.createQueueSession()" is likely going to actually be an instance of the "AQjmsSession" class, so I can cast to that, and then I can call "commit" or "rollback".
What is unclear from the javadoc description is what happens when "close()" is called on the session object. Does this do an implicit "commit()", perhaps unless "rollback()" has already been called?
I'm still a little uncertain about whether the scope of my transaction will be wide enough to protect everything that needs to be protected.
For instance, I assume that my transaction starts when my consumer (not in an application server) reads the message from the queue. At that point, my consumer does some "screen-scraping" work. When it's done, it will call a session bean on the application in the application server (separate JVM, in other words), which will create some EJB entity objects and also insert raw database rows. The session bean will then return, and then the original method which read a message from the queue will be completed.
What I need to know is what will happen if ANYTHING in that process fails, either in the external consumer, or in the session bean, or creating EJB entities? That is, will the entire transaction be rolled back, undoing the EJB entity creations AND the removal of the message from the message queue?
If this can possibly work, I'm assuming this would be utilizing an XA datasource, or a non-emulated data source (which I think means the same thing).

Create session bean using interfaces, not implementation classes

Hi,
I'm using interfaces and session beans for my persistence/data layer in my adf application.
I've created a data control for my session bean and during creation of this data control, javabean.xml files are created for the different interfaces that are used in my session bean.
If I create bindings on these methods, interfaces in jspx-documents I will get errors because he can't find the impl-classes that implement these interfaces.
When using interfaces in your session bean (as return values or parameters) instead of classes you need to manually create javabean.xml files for the implementation classes.
It's required by the databindings/datacontrol that the implementation-classes are described in a javabean-format as well? Is this a spec we need to adhere to?
Could someone verify that you need to create javabean.xml-files for as well the interfaces as the classes when you're working with interfaces in your session beans?
regards,
Nathalie

A patch was released by Oracle to be able to work with Interfaces and so it's not required to work with implementation-classes.
Patch for 5726754(Base bug 5657179)

JDeveloper 10.1.3 EA 1 Session Bean Problems

Hello,
it seems there are some problems in JDeveloper 10.1.3 EA1 related to Session EJBs:
1) The Create Session Bean Wizard doesn't work correctly. After finishing the Wizard, JDeveloper only creates the ejb-jar.xml and orion-ejb-jar.xml, but not the Session EJB classes/interfaces themselves (Bean, Remote, Home). So I had to develop the Session Bean in JDeveloper 10.1.3 Developer Preview. That worked fine. I finally migrated the project to 10.1.3 EA1.
2) When I try to run my JSF/EJB application with the Session Bean in 10.1.3 EA1, the following error occurred:
05/10/24 17:31:15 Error instantiating application 'current-workspace-app' at file: <a file path>...oc4j-app.xml:
Error initializing ejb-modules:
Error loading module file: <a file path>.../Model/classes/:
Syntax error in source or compilation failed in:
<a file path>...\Software\JDeveloper\jdevj2eebase1013\jdev\system\oracle.j2ee.10.1.3.34.12\embedded-oc4j\application-deployments\current-workspace-app\Umfragesystem02_Model_0\generated\CommandHandlerSession_StatelessSessionBeanWrapper0.java
I have no idea how to solve this problem. Does anybody have a solution?
Regards,
Matthias

Tested Session Bean and Entity Bean. 
The bean class and the deployment descriptors get 
generated. 
The remote/local, home/local home interfaces do not 
get generated. 
Thanks. The Session Bean Creation Wizard problem is a problem I could solve using a workaround. But the problem that really stems me is the error I receive when I try to run my webapp using the Session Bean and some more classes and JavaServer Faces files: 
 
Error instantiating application 'current-workspace-app' at file: ...oc4j-app.xml: Error initializing ejb-modules: 
Error loading module file: .../Model/classes/: 
Syntax error in source or compilation failed in: ...\Software\JDeveloper\jdevj2eebase1013\jdev\system\oracle.j2ee.10.1.3.34.12\embedded-oc4j\application-deployments\current-workspace-app\Umfragesystem02_Model_0\generated\CommandHandlerSession_StatelessSessionBeanWrapper0.java 
 
What goes wrong with JDeveloper or the application?

Using TableLocking API in Stateless Session Bean through WD application

Hi All,
We have develpoed a webDynpro application which involved Jav Dictionary Table.
We have given UI for Creation, Updation and Deletion of the table.For database connection we have used Stateless Session Bean.
we have the requirement of Locking the Table record when one user is either editing or deleting the record of Table from UI, so any other user cannot update or delete the same record.
To implement the above functionality, we have used TableLocking API with lifetime as userSession in the Stateless Session Bean to acquire a Lock for particular record.
With lifetime as usersession the record should get unLocked automatically, if the session of application is expired and record is not unLocked Explicitly.
We are calling the Session Bean from Webdynpro application to acquire a lock, When the Dynpro application expires the locked record should get unlocked automatically as the lifetime is defined as usersession,But the record remains unlocked only even after expiration of the application sessionand deadlock occurs for that record.
So if anyone can suggest the solution for the above problem.
Or some other method to Lock Particular Record from application.
Thanks in advance.
Regards,
Shruti.

HI,
Can you resolve this issue?
I have the same scenary, could you give me some tips?
Thanks,
Freddy F

How can i design a EJB application using session Beans?

Hello,
I am designing a Find application using EJB. Here a user is prompted a search page, where he can enter the search criteria's. Then on click of submit, the query is formed at the server side depending on what criteria's were selected. Then a jdbc query is performed and the results are returned back to the user. Here no session is maintained for the users. Can anyone suggest me how to design this application using EJB. Should i use entity beans for this or session beans will suffice? Should the jdbc query be performed in the bean itself or should it be outside in a helper class? Please kindlu suggest me the design for this application...
Regards,
Subbu

Hi,
First of all, I'm unable to figure out why you need to use EJB for this scenario. You can write a helper class to frame and execute the query.
If you really want to use EJB, then I suggest you use a stateless Session Bean with transaction attribute as TX_NOT_SUPPORTED. From the session bean, you can call the helper class. But, by avoiding the session bean, you can eliminate remote calls, thus improving your performance. Also, check if the database & the db driver you are using supports sql caching.
Regards,
Raj.

Error while adding a new method to the Session Bean

Hello everyone. I'm using jdev 11g, ejb, jpa & jsf. Everything works fine. But when I try to add a custom method to the Session Bean, I'm having an error.
Here is my steps:
1) I added a new method to SessionBean.java. Something like this:
public void Hello() {
System.out.println("Hello!");
2) Then using Structure palette I exposed this method through Local interface and created data control
3) Finally, I made a command button binded to this method (just droped it from DataControls.dcx to my page)
When I start the page and click the button, I'm having the following error:
Error 500--Internal Server Error
javax.faces.el.EvaluationException: Method not found: Hello.execute(javax.faces.event.ActionEvent)
 at org.apache.myfaces.trinidadinternal.taglib.util.MethodExpressionMethodBinding.invoke(MethodExpressionMethodBinding.java:58)
 at org.apache.myfaces.trinidad.component.UIXComponentBase.broadcastToMethodBinding(UIXComponentBase.java:1227)
 at org.apache.myfaces.trinidad.component.UIXCommand.broadcast(UIXCommand.java:183)
 at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:70)
... (I've truncated the log because there is nothing important in the missing part)

Yes, I have binding in the page def. Everything is correct there:
<methodAction id="Hello" RequiresUpdateModel="true" Action="invokeMethod"
MethodName="Hello" IsViewObjectMethod="false"
DataControl="PriceServiceLocal"
InstanceName="PriceServiceLocal.dataProvider"/>
I've droped the method from the Data Controls panel

Calling EJB 3.0 Stateless Session Bean

Dear all,
I created a stateless session bean with a hello world method on it. Now i want to call the method from a BeanDecorator class, through a getter metod. When i use the jndi lookup in my getter, i can call the helloWorld method without a problem. However, when i dont use the jndi lookup, and only use the @EJB annotation, i always get a nullpointer.
This is working:
InitialContext ic = new InitialContext();
test = (TestLocal)ic.lookup("test.be/ear~bd/LOCAL/TestBean/"+TestLocal.class.getName());
test.helloWorld()
This gives nullpointer:
@EJB
private TestLocal test;
test.helloWorld();
What is the correct way to consume session beans without having to explicitly code the jndi lookup?
Kind regards.

Hi,
any annotation like this can be used only in "managed classes" like Session Beans, Servlets etc. Managed classes are those classes managed by the J2EE server. Managed here means, lifetime controlled by server.
You can find this in J2EE specification.
Frank

EJB 3.0 - Communicate an Applet with a Session Bean

Hello
I'm developing an EJB 3.0 app (eclipse and glassfish tools bundle), and I have an applet that has to use remote session beans.
QUESTION: Is it possible for the applet to connect to EJB?
QUESTION: By creating a J2EE application client project, can I use @EJB annotations to inject the session bean directly to the applet, avoiding the JNDI lookup?
(since I imagine that the anwser to the second one is NO, I do the following consideration)
Given an application client project, I imagine that this application can run remotely on a client machine/JRE. Then this application can use Annotations/injection facilities whenever it runs on a J2EE client container (which I assume consists of a set of libraries provided by the application server vendor, Glassfish in that case). Could this application be deployed using Java Web Start? If so, why can't it be deployed as an applet? (both options run in a client JRE, don't they?).
QUESTION: In either case (applet or JWS), how do I have to package the JAR file (using Eclipse) so that it contains the needed libraries for accessing the EJB? Which are those libraries?
At the time being, I'm trying to implement a sample application that follows the "Applet doing JNDI lookup" approach. I have:
- an EAR project
- an EJB project (containing an Entity Bean and a Stateless Session Bean with a @Remote interface)
@Remote
public interface HelloRemote {
 public String hello(String name);
@Stateless
public class Hello implements HelloRemote {
 @Override
 public String hello(String name) {
 return "Hello "+name+"!!";
}- an Application Client project (containing the applet code):
public class ClientApplet extends JApplet {
 public void init(){
 try {
 Context jndiContext = getInitialContext( );
 HelloRemote server = (HelloRemote) jndiContext.lookup(HelloRemote.class.getName());
 setContentPane(new JLabel(server.hello("Gerard")));
 } catch (NamingException e) {
 // TODO Auto-generated catch block
 e.printStackTrace();
 private Context getInitialContext() throws NamingException{
 Properties props = new Properties();
 props.setProperty("java.naming.factory.initial", "com.sun.enterprise.naming.SerialInitContextFactory");
 props.setProperty("org.omg.CORBA.ORBInitialHost", "myhost");
 props.setProperty("org.omg.CORBA.ORBInitialPort", "3700");
 return new InitialContext(props);
}- a static web project (with a sample web page that contains the applet object the corresponding applet JAR file)
I tried to export the Application Client project as an "application client JAR", in the hope that the java EE libraries bundled with glassfish (listed as libraries of this project) would be packaged too.
No success, so now I'll try to copy all the JAR files (one by one) into the +\WebContent\+ folder of the Web Project, and add references to each of them in the archive="" attribute of the +<applet>+ HTML tag. Although this might work, I suspect that I am missing the good/easy way of doing it. Any suggestions?
Thanks in advance,
Gerard
Edited by: gsoldevila on May 6, 2009 7:09 AM

An Applet can communicate with an EJB via JNDI lookup but I would (personally) use an intermediate Servlet to handle this. Client to Servlet communication is http whereas to ejb is iiop - which might be blocked.
Injection only works in managed classes (EJB, Servlet, Listeners..) and an Application Client main class. So yes you could use an app client for handling resource injection.
m

Calling Enity Bean's business methods from a session bean in EJB 3.0 specif

Hello everybody,
Happy to be a member with you in this forum.
This is my first participation in this forum.
I have some problem to start with EJB 3.0 specification, I have created an entity bean with some business methods that access a mysql datbase, then i want to create a stateful session bean to provide the client an interface to consume business methods in Enity be
Please can someone you help me with an example

@Vladimir Pavlov
I did not understand what you are trying to convey...
Whenever an attribute of this bean is modified we want to access that latest value.... Is there any way to know, when the attribute is modified? Just with get/set we can not know, when it is modified... am i right?
We want to achieve this without modifying the existing source code of the EJB....
@ Ivo Simeonov
As of my knowledge, to use interceptors we need to modify the EJB source code, but we do not want to touch the source code....
All this has to be achieved dynamically when the application is deployed in the production.... is it possible???

How to use jta in toplink and stateless session bean EJB 3.0?

I have an application with techologies jsf,stateless session bean, adf, toplink
generated by toplink workbench.
In web side ı want to use two methods in stateless session bean which are updated
different tables. I call these methods in my page backing bean.
I also want to JTA in web side. My first methods is done correctly, but second method has an error. I wanto to rollback all transaction.
How can ı do that? with using JTA in Toplink...

Yuichi
Did you manage to solve this? I'm doing something similar and seeing the same problem, although they're up to 7.3 SP7.
Any help greatly appreciated.
Lewis

Problem calling a session bean (EJB 3.0)

Hello,
I'm new to netbeans and J2EE. I'm using NetBeans 5.5 Beta 2 and sun application server 9 pe.
I created a new enterprise application and i'm trying to access a Session Bean (Remote and Stateless)
from the app-client (outside the main class).
This is the loockup method that was generated by the IDE (Enterprise Resources > Call enterprise bean):
private ejb.SessionBeanDoenteRemote lookupSessionBeanDoenteBean() {
try {
javax.naming.Context c = new javax.naming.InitialContext();
return (ejb.SessionBeanDoenteRemote) c.lookup("java:comp/env/ejb/SessionBeanDoenteBean");
catch(javax.naming.NamingException ne) {
java.util.logging.Logger.getLogger(getClass().getName()).log(java.util.logging.Level.SEVERE,"exception caught" ,ne);
throw new RuntimeException(ne);
When I run the application and try to invoke the lookup method my application gets the following exception:
SEVERE: exception caught
javax.naming.NameNotFoundException: No object bound to name java:comp/env/ejb/Se
ssionBeanDoenteBean
at com.sun.enterprise.naming.NamingManagerImpl.lookup(NamingManagerImpl.
java:751)
at com.sun.enterprise.naming.java.javaURLContext.lookup(javaURLContext.j
ava:156)
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:307
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at intensivecare.entrada.JDialogEntrada.lookupSessionBeanDoenteBean(JDia
logEntrada.java:219)
at intensivecare.entrada.JDialogEntrada.buttonMenuGravarActionPerformed(
JDialogEntrada.java:79)
at intensivecare.JDialogWizzard$2.jButtonGravarActionPerformed(JDialogWi
zzard.java:178)
at componentes.JTaskPanelMenu$3.actionPerformed(JTaskPanelMenu.java:54)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:18
49)
at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.jav
a:2169)
Please... can someone help me?

The portable way to acquire the dependency is through java:comp/env or @EJB. Accessing the
global namespace directly is not recommended. If you use an ejb-ref, you need to define it
in the component environment within which you'll be looking up the dependency. So if you're
looking it up from an Application Client, you'll need to define the ejb-ref in application-client.xml.
Also, the ejb-ref-name is the portion of the string after java:comp/env. There is no automatic
"ejb" appended to it. If you do ic.lookup("java:comp/env/foo"), your ejb-ref-name would be "foo".
You can use @EJB but it can only be defined in certain managed classes such as the
Application Client main class.
You can find additional info in our EJB FAQ :
https://glassfish.dev.java.net/javaee5/ejb/EJB_FAQ.html
--ken

Creation of session bean

Similar Messages

Maybe you are looking for