Weblogic appears to have a big advantage over many competitors with its
Zero-Administration Client (ZAC). It seems that many of us (not all!)
haven't reached the point in EJB development where deployment is a concern.
BEA focused on deployment very early in their product lifecycle, probably as
a feature/benefit of using RMI and taking advantage of RMI's ability to
serialize classes across the wire on demand.
Some Questions:
1. Do any other EJB servers provide similar (or better) tools for managing
the remote deployment of applications?
2. What are some of the strategies used to push stub/helper classes out to
the clients? For example, if I add a method to an existing interface, all of
my applications that use the prior implementation should break, correct?
I was very disappointed to find that CORBA does not allow the dynamic
distribution of classes. For example, if I have a parameter of type
Employee<interface>, and I marshall a class that implements this interface,
the class that implements must be present on the client. There were many
times that I took advantage of RMI's ability to do this "on the fly".
I realize that these problems are not specific to EJB, however I think they
will become important to a great many of us as we start to move from testing
to deployment.
thanks,
jim
===========================================================================
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".
