-
1. Re: problem in : new InitialContext();
lothar Sep 15, 2001 8:37 AM (in response to mmft)From where is this code - an ejb, servlet, standalone client?
-
2. Re: problem in : new InitialContext();
nuanda Sep 16, 2001 8:03 AM (in response to mmft)Please post the jndi.properties that you are using...
-
3. Re: problem in : new InitialContext();
mmft Sep 16, 2001 10:16 AM (in response to mmft)i use standalone client..
-
4. i did not change anything..
mmft Sep 16, 2001 10:17 AM (in response to mmft)java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.provider.url=jnp://localhost:1099
java.naming.factory.url.pkgs=org.jboss.naming -
5. Re: problem in : new InitialContext();
s.hart Sep 17, 2001 5:41 AM (in response to mmft)Then you need jnp-client.jar on your classpath.
-
6. Re: problem in : new InitialContext();
juha Sep 17, 2001 7:08 AM (in response to mmft)Make sure you don't have Sun J2EE RI in your classpath when you run your client.
-
7. Re: problem in : new InitialContext();
cnsxxx09 Dec 12, 2001 9:35 AM (in response to mmft)Hi,
Out of curiosity, is it also possible with JBoss to use:
com.sun.enterprise.naming.SerialInitContextFactory
to create the InitialContextFactory?
Thanks
Chris
-=-= -
8. Re: problem in : new InitialContext();
cnsxxx09 Dec 13, 2001 9:12 AM (in response to mmft)I know that this is not possible with WebLogic without
either using IIOP or giving weblogic.jar to the clients (which means that, should the App Server be upgraded then all clients would need a new weblogic.jar file too!).
So, I assume that, similarily, it is not possible with JBoss either....hence the existence of jnp-client.jar
I stand to be corrected on this...
(when I started on this route I must admit that I never dreamt for one minute that using JNDI to lookup a bean would be so proprietary....sigh....)
C.
--