Error with stateless EJB

Hi,
I am new to WebLogic and I trying to learn it. I was doing an exercise with a stateless EJB I got from a book and get this error:
javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory. Root exception is java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory
     at java.net.URLClassLoader$1.run(URLClassLoader.java:198)
     at java.security.AccessController.doPrivileged(Native Method)
     at java.net.URLClassLoader.findClass(URLClassLoader.java:186)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:299)
That class is already in my class path and still does not work. I am using WLS 8.1 on a Linux Suse 9.0 OS, and my IDE is Eclipse. The code seems to be fine seems it is deployed flawlessly by the server. No errors, no warnings. I can post if some one needs to see it. Any ideas?
Thanks!

If anyone is interested, and since it seems to be a common anoying problem, the solution is to put the weblogic.jar files in the classpath, and all of the client ones as well.

Similar Messages

Error with javax.ejb.*

Hi,
I am new to J2EE. I downloaded j2sdk1.4.1_01, j2sdkee1.3.1, and Ant 1.3 on a Windows XP Home Edition platform. Downloaded as well the Tutorial; which what I was testing it with. In the very first example (converter) as I did "ant converter" to compile, it fired a couple of errors:
1. 16 Bit MS-DOS subsystem
C:\WINDOWS\system32\ntvdm.exe
Error while setting up environment for the application
It continues running and then says
2. package javax.ejb does not exist
I already checked my PATH several times and included <J2EE_HOME>\bin and also <J2EE_HOME>\bin\j2ee.jar
It did not work. What's going on? Any help would be appreciated.
Thanks!!

why is u r classpath J2EE_HOME\bin\j2ee.jar i guess it should under lib
J2EE_HOME\lib\j2ee.jar
hope this helps
pranav

Transaction problem with stateless EJB and DAO

Hi,
I'm using a stateless session bean with container managed transaction and I have a method, which updates a row via CMP entity bean and then calls stored procedure, using a DAO object, which has to use the updated data. Both calls must be done in one transaction. The problem is that the stored procedure doesn't see the changes made from the update via CMP EJB, but after the method exits the changes are in the database. I'm using WebSphere 4.0.3 and DB2 7.2. Method code example in the stateless bean:
public doIt(ValueObject vo) throws ... {
OrderPosRemote opr = getOrderPosRemote();
opr.update(vo);
getDAO().recalc(vo);
} catch (DAOException daoex) {
getSessionContext().setRollbackOnly();
And in the DAO:
public boolean recalc(...) throws DAOException {
Connection conn = getConnFromDataSource();
CallableStatement cstmt = conn.prepareCall("call ...(?,?)");
cstmt.execute();
... // close cstmt and release connection to the pool
Any help will be highly appreciated !

Hi meadandale,
this was my first guess too and I set this attribute in the session bean method, then into the update method of the CMP bean and "manually" to the connection object in the DAO like this:
conn.setTransactionIsolation(Connection.TRANSACTION_READ_UNCOMMITTED);
The isolation level is set correctly (IMHO), because when I comment the line above in the DAO, an exception is thrown stating that the isolation level can't be changed within a transaction.
Unfortenully this didn't help too. Should I set some special attribute to the database or connection pool additionally ?
I don't understand what is the problem actually - it is definitely one transaction and why this doesn't work is not very clear to me ...

NoInitialContextException error with simple EJB

I am trying some of the basic EJB excercises in Mark Wutka's Using Java 2 Enterprixe Edition. The EJB is deployed using the server that comes with the Sun ej2ee SDK.
When starting the client, I get
Exception: javax.naming.NoInitialContextException: Need to specify class
name in environment or system property, or as an applet parameter, or in
an application resource file: java.naming.factory.initial
I am confused about this, as I understood that when using the j2ee server, this parameter is already defined via the j2ee.jar library. The only reference to this error I could find stated that it would occur if the j2ee.jar file is not in the classpath. Unfortunately, it is in mine, so it doesn't help.
I've included the code for the ejb, but it's just generic code I've seen in lots of tutorials.
package usingj2ee.hello;
import java.util.*;
import javax.naming.*;
import javax.rmi.*;
public class TestHello
public static void main(String[] args)
try
/** Creates a JNDI naming context for location objects */
Context context = new InitialContext();
/** Asks the context to locate an object named "HelloWorld" and expects the
object to implement the HelloWorldSessionHome interface */
HelloWorldSessionHome home = (HelloWorldSessionHome)
PortableRemoteObject.narrow(
context.lookup("HelloWorld"),
HelloWorldSessionHome.class);
/** Asks the Home interface to create a new session bean */
HelloWorldSession session = (HelloWorldSession) home.create();
System.out.println("The default greeting is: "+
session.getGreeting());
session.setGreeting("Howdy!");
System.out.println("The greeting is now: "+session.getGreeting());
/** Destroy this session */
session.remove();
/** Now create a session with a different greeting */
session = (HelloWorldSession) home.create("Guten Tag!");
System.out.println("Created a new session with a greeting of: "+
session.getGreeting());
/** Destroy this session */
session.remove();
catch (Exception exc)
exc.printStackTrace();

Just now, I accidentally ran the client without stating the j2ee server, and got exactly the same error message.
I'm wondring if there's any server configuration I need to do that hasn't been done.

Compilation errors with CMP EJBs in OC4J

I have created several new EJB's in JDeveloper using the
EJB creation wizard. For most of them I chose the CMP Entity Beans from Tables wizard. Now I have already created some EJB's this way and have used them successfully. But for some reason when I try to start my OC4J, I get the following error messages for all my new EJB's:
Error creating table: java.sql.SQLException: ORA-00955: name is already used by an existing object
Why is this?

The out-of-the-box behaviour of OC4J is to try to create tables for CMP beans when they are deployed. It sounds like a redeployment may be occuring bwhen you restart OC4J which is causing it to try and create the tables.
I think that even though you see these error messages, the container will start and your beans will function.
You can do one of two things to alter this situation if you want
a) manually drop the tables from the db before you do the next deployment
b) set the default behaviour of OC4J to drop tables when an application is undeployed (which happens before a redeployment is done) -- this can be done by setting an additional attribute on the j2ee/home/config/application.xml file -- "autodelete-tables=true"
-steve-

Error in stateless-clustering in weblogic-ejb-jar.xml

Hi,
This is my <weblogic-ejb-jar.xml> and I see an error in <stateless-bean-is-clusterable>. Can anybody please help me regarding this.
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-ejb-jar xmlns="http://www.bea.com/ns/weblogic/10.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/10.0 http://www.bea.com/ns/weblogic/10.0/weblogic-ejb-jar.xsd">
<weblogic-enterprise-bean>
<ejb-name>Sample1</ejb-name>
<stateless-session-descriptor>
<pool>
<initial-beans-in-free-pool>10</initial-beans-in-free-pool>
</pool>
<stateless-clustering>
<stateless-bean-is-clusterable>TRUE</stateless-bean-is-clusterable>
</stateless-clustering>
</stateless-session-descriptor>
</weblogic-enterprise-bean>
<weblogic-enterprise-bean>
<ejb-name>Sample2</ejb-name>
<stateless-session-descriptor>
<pool>
<initial-beans-in-free-pool>10</initial-beans-in-free-pool>
</pool>
<stateless-clustering>
<stateless-bean-is-clusterable>TRUE</stateless-bean-is-clusterable>
</stateless-clustering>
</stateless-session-descriptor>
</weblogic-enterprise-bean>
<weblogic-enterprise-bean>
<ejb-name>Sample3</ejb-name>
<stateless-session-descriptor>
<pool>
<initial-beans-in-free-pool>10</initial-beans-in-free-pool>
</pool>
<stateless-clustering>
<stateless-bean-is-clusterable>TRUE</stateless-bean-is-clusterable>
</stateless-clustering>
</stateless-session-descriptor>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
I am using weblogic 10.3 and EJB 3.0 Can I include all the EJBs in a single <weblogic-ejb-jar.xml> file and can I put it in the EAR->EarContent->META-INF folder, where the application.xml and weblogic-application.xml files exist.
Basically, I am trying to include <initial-beans-in-free-pool> and <stateless-bean-is-clusterable> for each of my EJBs. Since there is no annotation equivalent for them in EJB 3.0, I had to include the <weblogic-ejb-jar.xml> file. I appreciate if anybody can suggest me if there is any annotation equivalent for these.
Thank you,
Sowmya

Hi,
1. please try with <stateless-bean-is-clusterable>true</stateless-bean-is-clusterable>
2. the EJB Specification requires "The deployment descriptor must be stored with the name META-INF/ejb-jar.xml in the ejb-jar file." So you shouldn't put the weblogic-ejb-jar.xml to EAR's META-INF folder.
3. <stateless-bean-is-clusterable> has a default value as "true". so you needn't specify it in your weblogic-ejb-jar.xml if you just want to have the "true" value.
4. default value of <initial-beans-in-free-pool> is 0. Since you're changing the default value, you'll have to specify it in weblogic-ejb-jar.xml. If you can put all EJBs in one ejb jar file, you can have only one weblogic-ejb-jar.xml in the META-INF folder of this ejb jar.
Thanks,
Amy

[EJB:011055]Error deploying the EJB with error that JNDI name already inuse

Hi,
I have written a trivial application consisting of 4 stateless beans and 1 MDB. The ear is developed from some code generator tool and works fine if I directly deploy on weblogic server 812.
But in order to learn Weblogic Workshop I created new Application and EJB project. Then I imported the EJB jar and provided other source files.
From Weblogic Workshop I could generate the ear successfully. But while trying to deploy the ear I get the following exception :
<16/03/2005 10:02:38 PM GMT+05:30> <Error> <Deployer> <BEA-149201> <Failed to complete the deployment task with ID 1 for the application hsbc.
weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: prepare failed for MCAppBEAN.jar
Module: MCAppBEAN.jar Error: Exception preparing module: EJBModule(MCAppBEAN.jar,status=NEW)
Unable to deploy EJB: StatelessBean from MCAppBEAN.jar:
<b>[EJB:011055]Error deploying the EJB 'StatelessBean(Application: hsbc, EJBComponent: MCAppBEAN.jar)', the JNDI name 'StatelessBeanHSBC' is already in use. You mu
st set a different JNDI name in the weblogic-ejb-jar.xml deployment descriptor for this EJB before it can be deployed.</b> at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2556)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2474)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:798)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:507)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:465)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
--------------- nested within: ------------------
<b>Can someone tell where have I made the mistake?</b>
thanks in advance.

Try to undeploy and un target the applcation via WLS console and they try to deploy it again. Or just try to redeploy it.

Stateless EJB (exposed only one fn) as a web service - Error illegal public

I have a stateless EJB which has 3 methods.
I expose one of them only as a web service.
But when I test my web service I receive an error...
500 Internal Server Error
Servlet error: The class blah.blah.I_EmpRemote contains illegal public methods.
These methods do not conform to the
restrictions imposed by the web service implementation
Offending methods:
public abstract blah.blah.Employee blah.blah.I_EmpRemote.GetEmployee(java.lang.String) throws java.rmi.RemoteException
public abstract blah.blah.Operator blah.blah.I_EmpRemote.GetOperator(java.lang.String,int) throws java.rmi.RemoteException
So does this mean .. I should make sure all or none of my methods of an EJB are exposed in the Web Service ?
Or I can resolve this in any other way ?
Thanks,
Krishna

Or is it becoz the two methods that it objected to were returning user-defined objects and not String, void, Integer ... that a web service can recognize !
But still ... why cannot it just ignore the methods that are not exposed ?
Can someone throw some light on this.
Thanks,
Krishna

Error with EJBs in oc4j

All of a sudden Im getting this error in the oc4j deployment:
Error: com.framework.business.bd.BusinessDelegateException: Error calling ServiceClassification EJB: com.framework.business.servicelocator.ServiceNotAvailableException: Could not connect to service: java.lang.ClassCastException: narrow() failed for class: org.openitsm.sr.facade.serviceclassification.ServiceClassificationHome. Check classpath to _iiopClient.jar containing stub classes
I didnt change any code or our administrator swears he didnt change any confirguration.
The code was working fine and then just stopped working.
Anyone seen this?

user517184,
You asked:
Anyone seen this?No, but allow me to make some suggestions.
Did you change anything in the database? Sometimes changing database objects, like triggers or tables or stored routines, can affect OC4J.
Did you try restarting OC4J?
Did you try undeploying and redeploying your application?
Sorry I cannot be of more help.
Good Luck,
Avi.

Stateless EJB 3.0 to webservice

Hello,
I'm using EJB 3.0 deployed on weblogic server 10. I can deploy Stateless EJB without any problem.
If I add a @WebService tag above my stateless bean, my deployment fails with the following error:
Exception activating module: EJBModule(EfanetTA_EJB.jar) Unable to deploy EJB: ProfilesFacade from EfanetTA_EJB.jar: Unable to deploy EJB: EfanetTA_EJB.jar from EfanetTA_EJB.jar: [HTTP:101216]Servlet: "WSEE_SERVLET" failed to preload on startup in Web application: "/BusinessManager". class: lu.efa.ejb.jaxws.FindProfilesById could not be found at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:272) at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:566) at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:513) at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:358) at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:245) at com.sun.xml.ws.server.EndpointFactory.createSEIModel(EndpointFactory.java:229) at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:161) at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:291) at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:315) at weblogic.wsee.jaxws.JAXWSServlet.registerEndpoint(JAXWSServlet.java:125) at weblogic.wsee.jaxws.JAXWSServlet.init(JAXWSServlet.java:64) at javax.servlet.GenericServlet.init(GenericServlet.java:241) at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:282) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(Unknown Source) at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:63) at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58) at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48) at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:504) at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1830) at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1807) at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1727) at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2890) at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:948) at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:353) at weblogic.wsee.deploy.WseeWebappModule.activate(WseeWebappModule.java:139) at weblogic.wsee.deploy.WSEEEjbModule.activate(WSEEEjbModule.java:371) at weblogic.wsee.deploy.WsEJBDeployListener.activate(WsEJBDeployListener.java:52) at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1414) at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:423) at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107) at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26) at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71) at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:63) at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26) at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212) at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154) at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104) at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:139) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:816) at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1223) at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:434) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200) at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
Thank's for your help.
Thomas

I am facing a new problem, i tried to create the folowing build script:
<project default="build_artefacts">
     <taskdef name="apt" classname="com.sun.tools.ws.ant.Apt">
          <classpath refid="jaxws.classpath" />
     </taskdef>
     <target name="compile-server">
          <echo message="Compiling server classes" />
          <javac destdir="target/classes" includes="**/com/**">
               <src path="com/b2winc/controlpanel/business/facade/customer" />
               <classpath refid="project.classpath" />
          </javac>
     </target>
     <target name="apt" depends="compile-server">
          <apt destdir="${build}" sourcedestdir="${generated}" sourcepath="${src}">
               <classpath refid="jaxws.classpath" />
               <source dir="${src}">
                    <include name="**com/b2winc/controlpanel/business/*.java" />
               </source>
          </apt>
     </target>
     <target name="build_artefacts" depends="apt">
          <echo message="${src}"></echo>
          <taskdef name="antwsgen" classname="com.sun.tools.ws.ant.WsGen"
               classpath="${src}jaxws/lib/jaxws-tools.jar" />
          <antwsgen
               sei="CustomerFacade" verbose="true"
               destdir="target/classes" sourcedestdir="target/temp" >
               <classpath path="jaxws.classpath"/>
          </antwsgen>
     </target>
     <path id="jaxws.classpath">
          <pathelement path="jaxws-ri-121/lib/jaxws-tools.jar" />
          <pathelement path="jaxws-ri-121/lib/jaxb-api.jar" />
          <pathelement path="jaxws-ri-121/lib/jaxb-impl.jar" />
          <pathelement path="jaxws-ri-121/lib/jaxws-api.jar" />
     </path>
</project>     I used this guideline: http://today.java.net/pub/a/today/2006/06/13/web-services-with-jax-ws-2.0.html
And i get the following error:
      [apt] An exception has occurred in apt (1.5.0_11). Please file a bug at th
e Java Developer Connection (http://java.sun.com/webapps/bugreport) after check
ing the Bug Parade for duplicates. Include your program and the following diagno
stic in your report. Thank you.
      [apt] java.lang.NoClassDefFoundError: com/sun/mirror/apt/AnnotationProcessorFactoryThe strange thing, that this class belongs to the tools.jar inside my JDK 5.
Thanks
Carlos

HOWTO: Using a BC4J Application Module in an Stateless EJB Session Bean

HOWTO: Using a BC4J Application Module in an Stateless EJB Session Bean
by Steve Muench
Overview
BC4J provides automatic facilities for deploying any application module as a stateful EJB session bean. If you want to leverage the features of your BC4J application module from a stateless EJB session bean, it's not automatic but it is straightforward to implement. This howto article explains the details.
For our example, we will create a stateless EJB session bean that uses a container-managed transaction. To keep things simple, let's assume the session bean has a single public method on its remote interface named createDepartment() with the following signature:
public void createDepartment(int id, String name, String loc) throws AppException
AppException is an example of an application-specific exception that our method will throw if any problems arise during its execution.The goal of this article is to illustrate how to use the BC4J application module named com.example.hr.HRApp as part of the implementation of this createDepartment method on our stateless enterprise bean. Let's assume that the HRApp application module has a view object member named Departments, based on the com.example.hr.DeptView view object, based on the familiar DEPT table and related to the com.example.hr.Dept entity object so our view can be updateable.
Creating the Stateless Session Bean
We can start by using the JDeveloper Enterprise Bean wizard to create a new stateless session bean called StatelessSampleEJB implemented by:[list][*]com.example.StatelessSampleEJBBean (Bean class)[*]com.example.StatelessSampleEJBHome (Home interface)[*]com.example.StatelessSampleEJB (Remote interface)[list]
We then use the EJB Class Editor to add the createDepartment method to the remote interface of StatelessSampleEJB with the signature above. We edit the remote interface to make sure that it also reflects that the createDepartment method thows the AppException like this:
package com.example;
import javax.ejb.EJBObject;
import java.rmi.RemoteException;
public interface StatelessSampleEJB extends EJBObject {
void createDepartment(int id, String name, String loc)
throws RemoteException,AppException;
}Before we start adding BC4J into the picture for our implementation, our StatelessSampleEJBBean class looks like this:
package com.example;
import javax.ejb.SessionBean;
import javax.ejb.SessionContext;
public class StatelessSampleEJBBean implements SessionBean {
public void ejbCreate(){}
public void ejbActivate(){}
public void ejbPassivate(){}
public void ejbRemove(){}
public void setSessionContext(SessionContext ctx){
public void createDepartment(int id, String name, String loc)
throws AppException {
    // TODO: Implement method here
}We can double-click on the ejb-jar.xml file in our project to see the XML deployment descriptor for the bean we just created:
<ejb-jar>
   <enterprise-beans>
      <session>
         <description>Session Bean ( Stateless )</description>
         <display-name>StatelessSampleEJB</display-name>
         <ejb-name>StatelessSampleEJB</ejb-name>
         <home>com.example.StatelessSampleEJBHome</home>
         <remote>com.example.StatelessSampleEJB</remote>
         <ejb-class>com.example.StatelessSampleEJBBean</ejb-class>
         <session-type>Stateless</session-type>
         <transaction-type>Container</transaction-type>
      </session>
   </enterprise-beans>
</ejb-jar>We need to add the extra <assembly-descriptor> section in this file to indicate that the createDepartment method will require a transaction. After this edit, the ejb-jar.xml file looks like this:
<ejb-jar>
   <enterprise-beans>
      <session>
         <description>Session Bean ( Stateless )</description>
         <display-name>StatelessSampleEJB</display-name>
         <ejb-name>StatelessSampleEJB</ejb-name>
         <home>com.example.StatelessSampleEJBHome</home>
         <remote>com.example.StatelessSampleEJB</remote>
         <ejb-class>com.example.StatelessSampleEJBBean</ejb-class>
         <session-type>Stateless</session-type>
         <transaction-type>Container</transaction-type>
      </session>
   </enterprise-beans>
   <assembly-descriptor>
      <container-transaction>
         <method>
            <ejb-name>StatelessSampleEJB</ejb-name>
            <method-name>createDepartment</method-name>
            <method-params>
               <method-param>int</method-param>
               <method-param>java.lang.String</method-param>
               <method-param>java.lang.String</method-param>
            </method-params>
         </method>
         <trans-attribute>Required</trans-attribute>
      </container-transaction>
   </assembly-descriptor>
</ejb-jar>
Aggregating a BC4J Application Module
With the EJB aspects of our bean setup, we can proceed to implementing the BC4J application module aggregation.
The first thing we do is add private variables to hold the EJB SessionContext and the instance of the aggregated BC4J ApplicationModule, like this:
// Place to hold onto the aggregated appmodule instance
transient private ApplicationModule _am = null;
// Remember the SessionContext that the EJB container provides us
private           SessionContext    _ctx = null;and we modify the default, empty implementation of the setSessionContext() method to remember the session context like this:
public void setSessionContext(SessionContext ctx){ _ctx = ctx; }We add additional constants that hold the names of the J2EE datasource that we want BC4J to use, as well as the fully-qualified name of the BC4J application module that we'll be aggregating:
// JNDI resource name for the J2EE datasource to use
private static final String DATASOURCE = "jdbc/OracleCoreDS";
// Fully-qualified BC4J application module name to aggregate
private static final String APPMODNAME = "com.example.hr.HRApp";We expand the now-empty ejbCreate() and ejbRemove() methods to create and destory the aggregated instance of the BC4J application module that we'll use for the lifetime of the stateless session bean. When we're done, ejbCreate() it looks like this:
public void ejbCreate() throws CreateException {
try {
    // Setup a hashtable of environment parameters for JNDI initial context
    Hashtable env = new Hashtable();
    env.put(JboContext.INITIAL_CONTEXT_FACTORY,JboContext.JBO_CONTEXT_FACTORY);
    // NOTE: we want to use the BC4J app module in local mode as a simple Java class!
    env.put(JboContext.DEPLOY_PLATFORM, JboContext.PLATFORM_LOCAL);
    env.put(PropertyConstants.INTERNAL_CONNECTION_PARAMS,DATASOURCE);
    // Create an initial context, using this hashtable of environment params
    InitialContext ic = new InitialContext(env);
    // Lookup a home interface for the application module
    ApplicationModuleHome home = (ApplicationModuleHome)ic.lookup(APPMODNAME);
    // Using the home, create the instance of the appmodule we'll use
    _am = home.create();
    // Register the BC4J factory to handle EJB container-managed transactions
    registerContainerManagedTransactionHandlerFactory();
catch(Exception ex) {
     ex.printStackTrace();
    throw new CreateException(ex.getMessage());
}and ejbRemove() looks like this:
public void ejbRemove() {
try {
    // Cleanup any appmodule resources before getting shutdown
    _am.remove();
catch(JboException ex) { /* Ignore */ }
}The helper method named reigsterContainerManagedTransactionHandlerFactory() looks like this:
private void registerContainerManagedTransactionHandlerFactory() {
SessionImpl session = (SessionImpl)_am.getSession();
session.setTransactionHandlerFactory(
    new TransactionHandlerFactory() {
      public TransactionHandler createTransactionHandler() {
        return new ContainerManagedTxnHandlerImpl();
      public JTATransactionHandler createJTATransactionHandler() {
        return new ContainerManagedTxnHandlerImpl();
}The last detail is to use the BC4J appmodule to implement the createDepartment() method. It ends up looking like this:
public void createDepartment(int id, String name, String loc)
throws AppException {
try {
    // Connect the AM to the datasource we want to use for the duration
    // of this single method call.
    _am.getTransaction().connectToDataSource(null,DATASOURCE,false);
    // Use the "Departments" view object member of this AM
    ViewObject departments = _am.findViewObject("Departments");
    // Create a new row in this view object.
    Row newDept = departments.createRow();
    // Populate the attributes from the parameter arguments.
    newDept.setAttribute("Deptno", new Number(id));
    newDept.setAttribute("Dname", name);
    newDept.setAttribute("Loc", loc);
    // Add the new row to the view object's default rowset
    departments.insertRow(newDept);
    // Post all changes in the AM, but we don't commit them. The EJB
    // container managed transaction handles the commit.
    _am.getTransaction().postChanges();
catch(JboException ex) {
    // To be good EJB Container-Managed Transaction "citizens" we have
    // to mark the transaction as needing a rollback if there are problems
    _ctx.setRollbackOnly();
    throw new AppException("Error creating dept "+ id +"\n"+ex.getMessage());
finally {
    try {
      // Disconnect the AM from the datasource we're using
      _am.getTransaction().disconnect();
    catch(Exception ex) { /* Ignore */ }
Building a Test Client
With the EJB-Tier work done, we can build a sample client program to test this new stateless EJB Session Bean by selecting the bean in the Oracle9i JDeveloper IDE and choosing "Create Sample Java Client" from the right-mouse menu.
When the "Sample EJB Client Details" dialog appears, we take the defaults of connecting to embedded OC4J container. Clicking the (OK) button generates the following test class:
import java.util.Hashtable;
import javax.naming.Context;
import javax.naming.InitialContext;
import com.example.StatelessSampleEJB;
import com.example.StatelessSampleEJBHome;
public class SampleStatelessSampleEJBClient {
public static void main(String [] args) {
    SampleStatelessSampleEJBClient sampleStatelessSampleEJBClient =
       new SampleStatelessSampleEJBClient();
    try {
      Hashtable env = new Hashtable();
      env.put(Context.INITIAL_CONTEXT_FACTORY,
              "com.evermind.server.rmi.RMIInitialContextFactory");
      env.put(Context.SECURITY_PRINCIPAL, "admin");
      env.put(Context.SECURITY_CREDENTIALS, "welcome");
      env.put(Context.PROVIDER_URL,
              "ormi://localhost:23891/current-workspace-app");
      Context ctx = new InitialContext(env);
      StatelessSampleEJBHome statelessSampleEJBHome =
           (StatelessSampleEJBHome)ctx.lookup("StatelessSampleEJB");
      StatelessSampleEJB statelessSampleEJB;
      // Use one of the create() methods below to create a new instance
      // statelessSampleEJB = statelessSampleEJBHome.create();
      // Call any of the Remote methods below to access the EJB
      // statelessSampleEJB.createDepartment( int id, java.lang.String name, java.lang.String loc );
    catch(Throwable ex) {
      ex.printStackTrace();
}We uncomment the call to the create() method and add a few calls to the createDepartment() method so that the body of the test program now looks like this:
// Use one of the create() methods below to create a new instance
statelessSampleEJB = statelessSampleEJBHome.create();
// Call any of the Remote methods below to access the EJB
statelessSampleEJB.createDepartment( 13, "Test1","Loc1");
System.out.println("Created department 13");
statelessSampleEJB.createDepartment( 14, "Test2","Loc2");
System.out.println("Created department 14");
try {
// Try setting a department id that is too large!
statelessSampleEJB.createDepartment( 23456, "Test3","Loc3");
catch (AppException ax) {
System.err.println("AppException: "+ax.getMessage());
}Before we can successfully run our SampleStatelessSampleEJBClient we need to first run the EJB bean that the client will try to connect to. Since Oracle9i JDeveloper supports local running and debugging of the EJB-Tier without doing through a full J2EE deployment step, to accomplish this prerequisite step we just need to right-mouse on the StatelessSampleEJB node in the System Navigator and select "Run". This starts up the embedded OC4J instance and runs the EJB right out of the current out path.Finally, we can run the SampleStatelessSampleEJBClient, and see the output of the test program in the JDeveloper log window:
Created department 13
Created department 14
AppException: Error creating dept 23456
JBO-27010: Attribute set with value 23456 for Deptno in Dept has invalid precision/scale
Troubleshooting
One error that might arise while running the example is that the database connection information in your data-sources.xml for the jdbc/OracleCoreDS datasource does not correspond to the database you are trying to test against. If this happens, then double-check the file .\jdev\system\oc4j-config\data-sources.xml under the JDeveloper installation home directory to make sure that the url value provided is what you expect. For example, to work against a local Oracle database running on your current machine, listening on port 1521, with SID of ORCL, you would edit this file to have an entry like this for jdbc/OracleCoreDS :
<data-source
    class="com.evermind.sql.DriverManagerDataSource"
    name="OracleDS"
    location="jdbc/OracleCoreDS"
    xa-location="jdbc/xa/OracleXADS"
    ejb-location="jdbc/OracleDS"
    connection-driver="oracle.jdbc.driver.OracleDriver"
    username="scott"
    password="tiger"
    url="jdbc:oracle:thin:@localhost:1521:ORCL"
    inactivity-timeout="30"
/>This is the data-sources.xml file that gets used by the embedded OC4J instance running in JDeveloper.
Conclusion
Hopefully this article has illustrated that it is straightforward to utilize the full power of BC4J in local mode as part of your EJB Stateless Session Beans using container-managed transaction. This example illustrated a single createDepartment method in the enterprise bean, but by replicating the application module interaction code that we've illustrated in createDepartment, any number of methods in your stateless session bean can use the aggregated application module instance created in the ejbCreate() method.
Code Listing
The full code listing for the SampleStatelessEJB bean implementation class looks like this:
* StatelessSampleEJB
* Illustrates how to use an aggregated BC4J application module
* in local mode as part of the implementation of a stateless
* EJB session bean using container-managed transaction.
* HISTORY
* smuench/dmutreja 14-FEB-2002 Created
package com.example;
import oracle.jbo.*;
import oracle.jbo.server.*;
import javax.ejb.*;
import oracle.jbo.domain.Number;
import oracle.jbo.common.PropertyConstants;
import java.util.Hashtable;
import javax.naming.InitialContext;
import oracle.jbo.server.ejb.ContainerManagedTxnHandlerImpl;
public class StatelessSampleEJBBean implements SessionBean {
// JNDI resource name for the J2EE datasource to use
private static final String DATASOURCE = "jdbc/OracleCoreDS";
// Fully-qualified BC4J application module name to aggregate
private static final String APPMODNAME = "com.example.hr.HRApp";
// Place to hold onto the aggregated appmodule instance
transient private ApplicationModule _am = null;
// Remember the SessionContext that the EJB container provides us
private           SessionContext    _ctx = null;
public void ejbCreate() throws CreateException {
    try {
      // Setup a hashtable of environment parameters for JNDI initial context
      Hashtable env = new Hashtable();
      env.put(JboContext.INITIAL_CONTEXT_FACTORY,JboContext.JBO_CONTEXT_FACTORY);
      env.put(JboContext.DEPLOY_PLATFORM, JboContext.PLATFORM_LOCAL);
      env.put(PropertyConstants.INTERNAL_CONNECTION_PARAMS,DATASOURCE);
      // Create an initial context, using this hashtable of environment params
      InitialContext ic = new InitialContext(env);
      // Lookup a home interface for the application module
      ApplicationModuleHome home = (ApplicationModuleHome)ic.lookup(APPMODNAME);
      // Using the home, create the instance of the appmodule we'll use
      _am = home.create();
      // Register the BC4J factory to handle EJB container-managed transactions
      registerContainerManagedTransactionHandlerFactory();
    catch(Exception ex) {
       ex.printStackTrace();
      throw new CreateException(ex.getMessage());
public void ejbActivate(){}
public void ejbPassivate(){}
public void ejbRemove(){}
public void setSessionContext(SessionContext ctx){ _ctx = ctx; }
public void createDepartment(int id, String name, String loc)
throws AppException {
    try {
      // Connect the AM to the datasource we want to use for the duration
      // of this single method call.
      _am.getTransaction().connectToDataSource(null,DATASOURCE,false);
      // Use the "Departments" view object member of this AM
      ViewObject departments = _am.findViewObject("Departments");
      // Create a new row in this view object.
      Row newDept = departments.createRow();
      // Populate the attributes from the parameter arguments.
      newDept.setAttribute("Deptno", new Number(id));
      newDept.setAttribute("Dname", name);
      newDept.setAttribute("Loc", loc);
      // Add the new row to the view object's default rowset
      departments.insertRow(newDept);
      // Post all changes in the AM, but we don't commit them. The EJB
      // container managed transaction handles the commit.
      _am.getTransaction().postChanges();
    catch(JboException ex) {
      // To be good EJB Container-Managed Transaction "citizens" we have
      // to mark the transaction as needing a rollback if there are problems
      _ctx.setRollbackOnly();
      throw new AppException("Error creating dept "+ id +\n"+ex.getMessage());
    finally {
      try {
        // Disconnect the AM from the datasource we're using
        _am.getTransaction().disconnect();
      catch(Exception ex) { /* Ignore */ }
private void registerContainerManagedTransactionHandlerFactory() {
    SessionImpl session = (SessionImpl)_am.getSession();
    session.setTransactionHandlerFactory(
      new TransactionHandlerFactory() {
        public TransactionHandler createTransactionHandler() {
          return new ContainerManagedTxnHandlerImpl();
        public JTATransactionHandler createJTATransactionHandler() {
          return new ContainerManagedTxnHandlerImpl();

Hi Steve, It4s me again;
About the question I made, I tried with a single assembly-descriptor tag and a single container-transaction tag in the deployment descriptor of the session bean and these were the results.
java.lang.NullPointerException
     void com.evermind.server.rmi.RMIConnection.EXCEPTION_ORIGINATES_FROM_THE_REMOTE_SERVER(java.lang.Throwable)
     java.lang.Object com.evermind.server.rmi.RMIConnection.invokeMethod(com.evermind.server.rmi.RMIContext, long, long, java.lang.reflect.Method, java.lang.Object[])
     java.lang.Object com.evermind.server.rmi.RemoteInvocationHandler.invoke(java.lang.Object, java.lang.reflect.Method, java.lang.Object[])
     java.lang.Object com.evermind.server.rmi.RecoverableRemoteInvocationHandler.invoke(java.lang.Object, java.lang.reflect.Method, java.lang.Object[])
     java.lang.Object com.evermind.server.ejb.StatelessSessionRemoteInvocationHandler.invoke(java.lang.Object, java.lang.reflect.Method, java.lang.Object[])
     void __Proxy1.modificaEnvoltura(java.lang.Integer, java.lang.Integer, java.lang.Integer, java.lang.Integer, java.lang.Integer, java.lang.Integer, java.lang.String)
     void SamplemdeController.envolturaControlEJBClient.main(java.lang.String[])
Then I tried with multiple assembly-descriptor tags each with a single container-transaction tag and the results were:
java.lang.NullPointerException
     void com.evermind.server.rmi.RMIConnection.EXCEPTION_ORIGINATES_FROM_THE_REMOTE_SERVER(java.lang.Throwable)
     java.lang.Object com.evermind.server.rmi.RMIConnection.invokeMethod(com.evermind.server.rmi.RMIContext, long, long, java.lang.reflect.Method, java.lang.Object[])
     java.lang.Object com.evermind.server.rmi.RemoteInvocationHandler.invoke(java.lang.Object, java.lang.reflect.Method, java.lang.Object[])
     java.lang.Object com.evermind.server.rmi.RecoverableRemoteInvocationHandler.invoke(java.lang.Object, java.lang.reflect.Method, java.lang.Object[])
     java.lang.Object com.evermind.server.ejb.StatelessSessionRemoteInvocationHandler.invoke(java.lang.Object, java.lang.reflect.Method, java.lang.Object[])
     void __Proxy1.modificaEnvoltura(java.lang.Integer, java.lang.Integer, java.lang.Integer, java.lang.Integer, java.lang.Integer, java.lang.Integer, java.lang.String)
     void SamplemdeController.envolturaControlEJBClient.main(java.lang.String[])
Finally I tried with a single assembly-descriptor and multiple container tags and the results were:
java.lang.NullPointerException
     void com.evermind.server.rmi.RMIConnection.EXCEPTION_ORIGINATES_FROM_THE_REMOTE_SERVER(java.lang.Throwable)
     java.lang.Object com.evermind.server.rmi.RMIConnection.invokeMethod(com.evermind.server.rmi.RMIContext, long, long, java.lang.reflect.Method, java.lang.Object[])
     java.lang.Object com.evermind.server.rmi.RemoteInvocationHandler.invoke(java.lang.Object, java.lang.reflect.Method, java.lang.Object[])
     java.lang.Object com.evermind.server.rmi.RecoverableRemoteInvocationHandler.invoke(java.lang.Object, java.lang.reflect.Method, java.lang.Object[])
     java.lang.Object com.evermind.server.ejb.StatelessSessionRemoteInvocationHandler.invoke(java.lang.Object, java.lang.reflect.Method, java.lang.Object[])
     void __Proxy1.modificaEnvoltura(java.lang.Integer, java.lang.Integer, java.lang.Integer, java.lang.Integer, java.lang.Integer, java.lang.Integer, java.lang.String)
     void SamplemdeController.envolturaControlEJBClient.main(java.lang.String[])
How can I make my Stateless Session bean work out?

Javax ejb CreateException: Could not create stateless EJB

Hi,
I have a JavaEE (EJB3.0) project deployed on glassfish2.1 as -.ear (exported from eclipse3.4 to the autodeploy-folder) with -.ejb.jar, -.webui.war, general-lib-base.jar (some other...)
The session bean is invoked by a jsf-managed bean. Have a pure annotation +@ejb+ in managed bean (identifiing the ejb-interface (+@Remote+) ...the ejb is annotated with +@stateless+
get the following error message:
*...nested exception is: javax.ejb.CreateException: Could not create stateless EJB*
as beginner in the JavaEE-field I'm looking for some help concerning the possible causes.
thank's for any comment...
(also posted in the Enterprise JavaBeans-forum possibly better there)

problem fixed: in the deployment-descriptor ejb-jar.xml a spezification of the session-bean hung around ...very annoying!

Implementing Web Service with Stateless Session Bean

I have a web service that I've built using the WorkSpace Studio tools (create a WSDL, generate the Java code from the WSDL, fill in the skeleton methods in the service implementation class). This service is deployed as a web module within an EAR to WebLogic Server 10.0 and is working great as a web service.
I'd like to be able to also call the operations on this service via an EJB interface (from a different application on the same server). I followed the guidelines for adding EJB annotations to the web service implementation class (from [http://edocs.bea.com/wls/docs100/webserv/jws.html#wp215790]). I added the @Session annotation to the class, implemented javax.ejb.SessionBean, and added the ejbXXX() methods. This all makes perfect sense, and looked like it was going to work. However, WorkSpace Studio now gives me a compile error on the class that says "EJB backed WebServices are not supported."
A few internet searches for that error didn't return anything relevant.
It seems like I followed the instructions correctly. Is there a better way to build a service like this that is both a web service endpoint and a stateless session bean?
Thanks!
-Eric

Having separate EJB and web modules certainly makes things easier, but I have non-trivial (i.e. not feasible to copy) application logic that I'd like to expose with both a bean interface (for intra-application usage) and a web service interface (for public consumption).
I've tried starting with a "web application" WorkSpace Studio project and adding bean annotations. This produces the error I originally described. I also tried starting with an "EJB" WorkSpace Studio project and adding web service annotations. This fails at deployment time with errors about missing web service descriptors (the error is correct - the web-service-related descriptor elements are missing from the deployment descriptors).
The documentation explicitly presents this as an option (annotating a class with both web service and session bean annotations), but how does one actually make this work?

WebService annoated with @stateless does not deploy in WLS11g

To facilitate the packaging and the deployment of a web service, i annotate it with the @stateless annotation. In this way the web service is packaged with all my others ejb in the same jar. When i deploy the jar that is also packaged in an ear, i have got the following error message :
Unable to find ejb-jar with uri lock-impl in ear at D:\cless2009\CoreBuild\out\lib\WLS_cless\wls_cless.ear
This is part of the code of my web service :
@Stateless
@WebService(name = "ChangeStatus", targetNamespace = "http://cless.gemalto.com/ChangeStatus")
@XmlSeeAlso({
ObjectFactory.class
public class ChangeStatusWS implements ChangeStatus
As you can see, the web service is also annotated with @stateless but without any @Local or @Remote definition.
the jar does not contain any ejb-jar.xml, weblogic-ejb-jar.xml.
Can you tell me what's wrong with this way of doing things ?
Some help would be appreciated. Thanks.

See here under my application.xml
<?xml version="1.0" encoding="ASCII"?>
<application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:application="http://java.sun.com/xml/ns/javaee/application_5.xsd" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd" version="5">
<display-name>ClessServer</display-name>
<module>
<ejb>util.jar</ejb>
</module>
<module>
<ejb>repository-impl.jar</ejb>
</module>
<module>
<ejb>workflow-impl.jar</ejb>
</module>
<module>
<ejb>swift-listener.jar</ejb>
</module>
<module>
<ejb>counters-impl.jar</ejb>
</module>
<module>
<ejb>perso-impl.jar</ejb>
</module>
<module>
<ejb>serviceDelivery-impl.jar</ejb>
</module>
<module>
<ejb>lock-impl.jar</ejb>
</module>
<module>
<ejb>deletion-impl.jar</ejb>
</module>
<module>
<ejb>customerCare-impl.jar</ejb>
</module>
</application>
and my weblogic-application.xml :
<?xml version="1.0" encoding="UTF-8"?>
<wls:weblogic-application xmlns:wls="http://www.bea.com/ns/weblogic/weblogic-application" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/javaee_5.xsd http://www.bea.com/ns/weblogic/weblogic-application http://www.bea.com/ns/weblogic/weblogic-application/1.0/weblogic-application.xsd">

<wls:application-param>
<wls:param-name>webapp.encoding.default</wls:param-name>
<wls:param-value>UTF-8</wls:param-value>
</wls:application-param>
</wls:weblogic-application>
The lock-impl.jar is in my ear at the root of the ear file.
Edited by: fmosse on 11 août 2009 04:38

Deploy a stateless ejb (an easy one)

Hi all,
deploying a stateless ejb I've got this error in
the calling code (that's in the servlet calling)
-- begin error---
com.evermind.server.rmi.OrionRemoteException: admin is not allowed to call this EJB method, check your security settings (method-permission in ejb-jar.xml and security-role-mapping in orion-application.xml).
--- end error---
sounds as if the role ADMIN was not authorized. Where should
I look for info?
daniele rizzi

Hi Daniele,
I don't know if this will help you, but I suggest you point your web
browser at this URL:
http://kb.atlassian.com/search.jsp
and do a search on "principals.xml"
As the error message suggests, you need to check the following files
(that are all located beneath the root OC4J installation directory):
principals.xml
ejb-jar.xml
orion-ejb-jar.xml
orion-application.xml
application.xml
web.xml
orion-web.xml
Note that there may be several versions of any of the above files
in different directories. You need to locate the ones that are relevant
to your problematic app. I found that these files are laid out in a
fairly intuitive way -- I didn't have much trouble figuring out what
should be in each file by looking at the sample applications that
Oracle supply either with the OC4J distribution, or from the "Technet"
website.
I'm pretty sure you'll be able to figure it out if you go through
the information sources I've listed above.
Hope this helps you.
Good Luck,
Avi.

Error with stateless EJB

Similar Messages

Maybe you are looking for