jaikiran pai [
http://community.jboss.org/people/jaikiran] created the discussion
"Re: JNDI Standalone client"
To view the discussion, visit:
http://community.jboss.org/message/597848#597848
--------------------------------------------------------------
Wolfgang Knauf wrote:
I took a look at the sample at
http://docs.jboss.org/jbossas/docs/Server_Configuration_Guide/4/html/Writ...
http://docs.jboss.org/jbossas/docs/Server_Configuration_Guide/4/html/Writ...
It uses the "NonSerializableFactory":
http://docs.jboss.org/jbossas/javadoc/4.0.2/org/jboss/naming/NonSerializa...
http://docs.jboss.org/jbossas/javadoc/4.0.2/org/jboss/naming/NonSerializa...
The JavaDoc of this class states:
A utility class that allows one to bind a non-serializable object into a
#local JNDI context. The binding will only be valid for the lifetime of the
#VM in which the JNDI InitialContext lives
A utility class that allows one to bind a non-serializable object into a
#local JNDI context. The binding will only be valid for the lifetime of the
#VM in which the JNDI InitialContext lives
"A utility class that allows one to bind a non-serializable object into a local JNDI
context. The binding will only be valid for the lifetime of the VM in which the JNDI
InitialContext lives"
To my understanding, this means that you can lookup the bound data only if your process
is in the same VM. But a standalone client will not be able to see it.
That's
correct!
--------------------------------------------------------------
Reply to this message by going to Community
[
http://community.jboss.org/message/597848#597848]
Start a new discussion in Beginner's Corner at Community
[
http://community.jboss.org/choose-container!input.jspa?contentType=1&...]