Hi L,
Success at last after having upgraded JBoss to 4.0.5 (full support for EJB 3.0)
which may have fixed the problem. Anyhow the main sticking point was not
referencing TravelAgentBean correctly using JNDI. Below is the only slight
modification needed from the original code from the Client:
The main problem results from inability to initialize the context, see the
exception:
Need to specify class name in environment or system property:
java.naming.factory.initial
Some properties must be set prior to creation of InitialContext instance. The
other way of setting the properties is
You must initialize the context environment. The following code works with
JBoss AS 4 (EJB2.1 module is deployed):
package accessejb;
import a.AccessibleSessionRemote;
import a.AccessibleSessionRemoteHome;
import java.util.Hashtable;
import javax.naming.InitialContext;
import
[should have been in the previous reply]
/client/jboss-j2ee.jar
/client/jbossall-client.jar
/server/default/lib/jnpserver.jar
/lib/jboss-common.jar
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4013035#4013035
Reply to the post :
[server]/client/jboss-j2ee.jar
[server]/client/jbossall-client.jar
[server]/server/default/lib/jnpserver.jar
[server]/lib/jboss-common.jar
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4013036#4013036
Reply to the post :
Try to replace 'DefaultDS' by 'java:/DefaultDS' in persistence.xml.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4012322#4012322
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4012322
Hi L,
By prepending the java:/ to DefaultDS in persistence.xml file did fixed the
binding issue. I have tried this in the past but did not redeploy correctly.
Anyhow, I now receive the following error when running the Client.java on the
titan.jar EJB:
javax.naming.NoInitialContextException:
