>
> It is WAY cooler. Good god, we are so fucking "hip" it hurts... I never
> knew we could be soooo cool... I never knew.
>
> marc
Let me translate Marc's high level description down a level or two.
1. When a bean is deployed a container invoker object is created to handle requests.
By default this is a org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker instance
which is an RMI object. It creates a delegate object that handles VM version
differences
during initialization. The 1.3 VM delegate is
org.jboss.ejb.plugins.jrmp13.server.JRMPContainerInvoker.
2. When the RMI JRMPContainerInvoker is started it exports itself as a remote object
and then binds a Proxy that implements the bean's home and javax.ejb.Handle
interfaces into JNDI under the EJB jndi name. The Proxy object is obtained from the
VM version delegate and uses an InvocationHandler that is a type of
org.jboss.ejb.plugins.jrmp.interfaces.HomeProxy. This is an Externalizable object that
has a reference to the RMI JRMPContainerInvoker.
3. When a client looks up the home interface from JNDI, they receive a copy of this
HomeProxy. The standard EJBHome methods are handled by the proxy, most of
them locally on the client side. Any bean specific methods are delegated to the RMI
version of the JRMPContainerInvoker that the proxy has a reference to.
I don't know anything about Python proxies so I can't say which is cooler, but this
is cool.
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
