> > 3 Don't generate any stubs (EJBoss)
> >
> > The main difference is in administration, and should be hardest with 1
> > and easiest with 3.
>
> The use of java.lang.reflect.Proxy (or "no stubs") in EJBoss is really nice but
> as I understand it you still need to dynamically or manually load the proxy
> handlers to communicate back to the server. The java.lang.reflect.Proxy provides
> you with a dynamic proxy generation on the client VM (providing your using JDK
> 1.3) but it doesn't eliminate the need for an InvocationHandler that smart
> enough to connect to the server and handle things like transaction propagation
> and communication of method invocations. Of course, I'm basing my assessment on
> EJBoss model from a few months ago and this may have changed. If not, I don't
> think your use of java.lang.reflect.Proxy buys you much.
Yes, but this is a "oneshot" thing which never changes. If you have an
application that uses EJBoss you bundle ejbossclient.jar with it, and
then it will be able to call all EJB's in any EJBoss server without any
need for dynamic class downloading. So I would say that the gain is big.
There's also no issues with managaing the actual stub files on the
server, and they're generated very fast which is good for development
(your typical stub generation tool takes awhile to do this, whereas
dynamic proxy generation takes about a second).
/Rickard
--
Rickard Öberg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
http://www.dreambean.com
Question reality
===========================================================================
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".
