Hi,
I took a look at the sample at http://docs.jboss.org/jbossas/docs/Server_Configuration_Guide/4/html/Writing_JBoss_MBean_Services-A_Standard_MBean_Example.html
It uses the "NonSerializableFactory": http://docs.jboss.org/jbossas/javadoc/4.0.2/org/jboss/naming/NonSerializableFactory.java.html
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.
There is a class "Util", which has a bunch of methods to work with JNDI bindings ( http://docs.jboss.org/jbossas/javadoc/4.0.2/org/jboss/naming/Util.java.html ) - maybe they allow binding to non-local VM, but I don't know this much about JNDI internal to provide further help.
Best regards
Wolfgang