Rickard �berg wrote:
>
> Problem:
> EJBObject extends Remote, thus only making it possible for the server to
> hand out stubs to RMI-objects. It is desirable to have the option of
> sending a Serializable proxy implementing the bean interface instead, in
> order to implement fault-management, load balancing, lazy-caching etc.
> That would also make it possible to implement EJB over plain JRMP (which
> is not an option currently due to the new design of 1.2-RMI).
>
For EJB server we only need client transparency, server part is
generated. So JDK 1.2 compatible variant is to call methods with
additional argument instead of direct corresponding method.
For example remote interface has test() method then server will
have two methods test() and test(Context ctx) (the method is
contained in additional interface TestEx). test() in stub just
gets a context and call test(Context ctx) on server. So everything
is working. I tested this variant with JDK 1.2 beta4.2. I have not
tested if test() method on server could be eliminated at all.
I have not found my test example (I performed this tests in october)
so I cannot send you source code. But believe that my work can
be easily reproduced. You can contact me if you need more details.
Now JDK1.2 documentation contains all information needed for
generating such stubs (it was not so in JDK 1.2 beta4.2).
During communication with JavaSoft on this issue, I was told
that JavaSoft plan to add API hooks to RMI for solving this
problem.
Constantine
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
