[JBoss-user] [Installation Configuration] - Re: javax.naming.NameNotFoundException: comp not bound

2005-01-11 Thread peake
The Answer: These are the properties: -Djava.naming.factory.initial=org.jnp.interfaces.NamingContextFactory -Djava.naming.provider.url=jnp://JBOSS_HOST:1099/ -Djava.security.auth.login.config=login.conf The login.conf file, pointed to by ?java.security.auth.login.config?, needs to contain:

[JBoss-user] [Installation Configuration] - Re: javax.naming.NameNotFoundException: comp not bound

2005-01-11 Thread wmprice
There is a reason for this: the java:comp/env namespace is reserved for application components running in a managed environment. What this basically means is that each application component has its own private namespace bound to the context of java:comp/env. When running outside of the

[JBoss-user] [Installation Configuration] - Re: javax.naming.NameNotFoundException: comp not bound

2005-01-11 Thread [EMAIL PROTECTED]
Use the global JNDI namespace in JBoss. Don't bind to java:/ View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3861615#3861615 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3861615