[
https://jira.jboss.org/jira/browse/JBMICROCONT-418?page=com.atlassian.jir...
]
David Lloyd commented on JBMICROCONT-418:
-----------------------------------------
A cool way to do this would be to have a Remoting 3 configuration which exposes the bean
via the new R3 transporters (which is sort of like RMI except it doesn't suck). Might
even be able to get that done by CR1 in fact....
Access MC bean remotely in a type safe manner
---------------------------------------------
Key: JBMICROCONT-418
URL:
https://jira.jboss.org/jira/browse/JBMICROCONT-418
Project: JBoss Microcontainer
Issue Type: Feature Request
Components: AOP
Reporter: Galder ZamarreƱo
Provide a mechanism to access an MC bean remotely in a type safe manner.
Currently, the only way to access an MC bean remotely is to add a @JMX annotation to it
and use the
RMIAdaptor method explained in
http://www.jboss.org/community/docs/DOC-9901 to access the
bean.
Another possibility is to bind the MC bean to JNDI via @JNDI annotation but looking up
the bean effectively
serializes the bean and sends it back to the client. Any invocations on the bean are
local to client.
One solution would be to either enhance @JNDI annotation or add an MC remote annotation
that indicates
the JNDI name and the remote proxy class so that MC creates a remote proxy for the bean
and binds the
proxy itself in JNDI. Clients would then be able to look up the proxy and use it to call
the MC remotely in a
type safe manner.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira