User development,
A new message was posted in the thread "Remote vs. Local client lookup of same JNDI
object":
http://community.jboss.org/message/525135#525135
Author : Brian Stansberry
Profile :
http://community.jboss.org/people/bstansberry@jboss.com
Message:
--------------------------------------------------------------
If you can put your remote client in a debugger and put a breakpoint in the
org.jnp.interfaces.NamingContext.lookup(Name) method, that's probably your best
approach to figuring out what's going on.
I don't know what version you're using so won't quote line numbers, but a
breakpoint here would be good:
res = naming.lookup(n);
That shouldn't return null. Then the code drops out of a try/catch block and goes
through a bunch of if tests to deal with various types of objects that can be returned,
resolve javax.naming.Reference etc. What will happen here very much depends on what was
bound into JNDI.
--------------------------------------------------------------
To reply to this message visit the message page:
http://community.jboss.org/message/525135#525135