I don't understand how the two flavours of invoke defined in ContainerRemote can be used to provide local (i.e. same JVM) call optimization ?
The reference to an instance of ContainerRemote that is aggregated by GenericProxy is used to make calls to an EJB, and a choice is made between two versions of invoke, one that takes a MarshalledObject and the other that takes explicit parameters describing the method invoked. Even if the instance of the GenericProxy is on the server side, if the ContainerRemote reference has been exported to the RMI run-time, the all calls to methods on the object will go via the _Stub and TCP/IP stack, regardless of the type of the method arguments ? Can someone enlighten me.
you again? oh wow, only 2 posts and they are the same crossposted to the news and here, you are a funny guy,
anyway like I said come to the Boston training for an in-depth walkthrough of the reason behind the magic in RMI/serialization of proxies, he he,