So this means you do need a jndi.properties file in the classpath when running the client?
After even more research, I found out that the jndi.properties file in the server/default/conf directory isn't right... It seems you need a line like this as well: java.naming.provider.url=localhost As for the classpath, it seems you need the client/jbossall-client.jar to be included as well, and then the client will run... Is there a place where this is explained? I mean, I found out about all this just browsing the web, but isn't there some simple document about "running my first ejb client" or something? Thanks, Hans On Sun, 2002-11-17 at 19:33, G.L. Grobe wrote: > >I'm using the same "java" command to launch jboss as I use to launch the > >client, so I'm pretty sure this is the case... So why am I still getting > >this exception? > > So in other words ... it sounds like you're launching two instances of the > JVM and of course that would be done using the same command, but ... > > >"When you use the JNDI API within the same VM that the JBoss server is > >running do not have to perform any special configuration to create a > >JNDI InitialContext. You simply create an InitialContext without any > >arguments." > > You have one for the JBoss server, and one for the client. Can you see how > you're not using the same VM? > > > > > ------------------------------------------------------- > This sf.net email is sponsored by: To learn the basics of securing > your web site with SSL, click here to get a FREE TRIAL of a Thawte > Server Certificate: http://www.gothawte.com/rd524.html > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user >
signature.asc
Description: This is a digitally signed message part
