-
1. Re: Question about InitialContext.lookup on a JNDI server.
peterj Jun 13, 2009 12:21 PM (in response to fredfred)JBoss 5.4.0.GA??? Is that a typo? Did you mean JBoss AS 5.1.0.GA?
-
2. Re: Question about InitialContext.lookup on a JNDI server.
fredfred Jun 13, 2009 8:40 PM (in response to fredfred)Yup, I did a typo.
My questions are:
-Where is JBoss 5.1.0.GA 's JNDI server?
-Is it accessable by class files in a Jar?
-What JAR/classes are in question?
-May this JNDI server be detached from JBoss, and
run on a server all it's own?
:) -
3. Re: Question about InitialContext.lookup on a JNDI server.
peterj Jun 14, 2009 5:38 PM (in response to fredfred)As far as I know, there is no way to extract the JNDI server.
-
4. Re: Question about InitialContext.lookup on a JNDI server.
peterj Jun 14, 2009 5:41 PM (in response to fredfred)I guess I am not sure about how to respond to you first three questions because it is of course accessible by client apps. Are you perhaps asking which JAR file(s) in the client directory handle(s) the JNDI chores?
-
5. Re: Question about InitialContext.lookup on a JNDI server.
fredfred Jun 14, 2009 8:03 PM (in response to fredfred)Yes, that's it!
particularly the JBoss classes needed for client java program
access,
"EJBSergerContextFactoryClass" etc,
needed for a separate client machine
to successfully initialise
InitialContext. -
6. Re: Question about InitialContext.lookup on a JNDI server.
peterj Jun 15, 2009 12:21 PM (in response to fredfred)The simple answer: include all of the JARs in the client directory.
If you want the minimum set of JARs, you can use JBoss Tattletale (under Projects | Tools in the tabs at the head of this web page) . Tatttletale provides various dependency reports that will help you determine exactly which JARs you need.