There are two issues here. The first is simply that the default jndi.properties file
does not contain the correct java.naming.factory.url.pkgs property value. It
is missing the org.jnp.interfaces package prefix which is where the jnp url
context factory is located. This is the correct jndi.properties file:
java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
#java.naming.provider.url=localhost
java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
The second issue is that the url context factory returned by the jnpURLContextFactory
is not capable of resolving remote jnp urls because of the premature binding
of the naming server inside the NamingContext ctor. This is due to a relatively
recent change that I don't see justification for.
The jndi.properties file has been fixed in the main branch. I will fix the other issue.
A bug id of 419015 has been created for this problem.
----- Original Message -----
From: "Anatoly Akkerman" <[EMAIL PROTECTED]>
To: "JBoss-Dev" <[EMAIL PROTECTED]>
Sent: Wednesday, April 25, 2001 1:54 PM
Subject: [JBoss-dev] Bug in jnp (handling references to remote JNDI servers)
>
> It seems to me that there is a bug in JNP NamingContext.checkRef() method
>
> Here is when I encounter
>
> BeanA is on host1, JBoss1
> BeanB is on host2, JBoss2
>
> BeanA is supposed to call BeanB, so it has an entry in jboss.xml that maps
> <ejb-ref>ejb/BeanB</ejb-ref>
>
> to <jndi-name>jnp://host2:port/testapp/BeanB</jndi-name>
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development