you really want to look at the first one. (The second one is for handles)
We bind a home in the JNDI tree. When someone accessses the object he gets
a ref to a proxyHome that can talk to the container through the
JRMPContainerInvoker.
The EJBObject are created on demand only when "create" or "find" are called
on the CI and container.
Essentially we bind the home under name (spec) and we create bit by bit
after that.
The reason we ask the CI for the home is that the CI is aware of the
particular invocation stack. (RMI/IIOP/SOAP)
marc
|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Tran, Leo CECOM SEC
|Sent: Friday, December 22, 2000 8:00 AM
|To: 'jBoss Developer'
|Subject: [jBoss-Dev] HomeProxy????
|
|
|
|How does HomeProxy work?
|
|Would someone describe the whole scenario from binding .....
|
|class JRMPContainerInvoker
| ........
| rebind( context, container.getBeanMetaData().getJndiName(),
|
|((ContainerInvokerContainer)container).getContainerInvoker().getEJBHome());
|
| // Bind a bare bones invoker in the JNDI invoker naming space
| rebind( context, "invokers/"+container.getBeanMetaData().getJndiName(),
| ((ContainerInvokerContainer)container).getContainerInvoker());
| ........
|
|until client try to access the EJBHome and EJBObject?
|
|
|Thanks,
|
|
