this is available as part of some of the new JMX Remoting code in head. This is being refactored to be more generic for different types of invocations, not just JMX - and this is being targeted for JB4. Stay tuned for more details.
Currently, we support pluggable detection and connectors for remote JBoss servers. Out of the box support for multicast, HA JNDI and unicast for detectors - and Sockets, RMI, and SOAP for connectors (more will be included in the future).
We are also working on support for JSR 160 - however, the spec is really lagging behind the featureset we already have.
Thanks for reply.
We have decided to go with an EntityBean that binds its handle to a remote JNDI service, and is managed through an MBean - gives us equivalent functionality for now.
Actually, we've had to abandon this too.
In our naive newbie understanding we thought that the Handle contained everything required to find the remote object.
But it doesn't. It only contains the name of the remote object - no context, address, etc...
So, back to square one for us :-(
You can always bind your own MBean handle to JNDI which contains the information you need to connect to the MBean server. All you need is a serializable object with a property list.
Yes, that is true.