Scott M Stark wrote:
> Let's get a discussion on J2EE ear deployment going and come to an
> agreement on how this should be implemented. Toby, what are your
> thoughts on the deployer rewrite?
Not ready, is what they are. I'm still trying to understand Dr Jung's
classloading/dependency prototype. This is something that I think will
sit above the actual EAR deployment code, so we can probably just leave
it out for the purposees of this discussion.
Pretty much all I have in mind so far is that the EAR deployer doesn't
want to keep a hard-coded list of the type of modules that it can
deploy, although I'm not sure that that's even the best idea because it
is pretty clearly specified what an EAR can contain.
So, perhaps there needs to be a general deployer that knows how to
deploy anything for which a deployer is registered. The EAR deplyer will
be one of these and it can then pass the deployment of EJB-JARs, WARs,
RARs and whatever else back to the general deployer.
I haven't given this enough thought to know if it will work with the
complex application deployment that Dr Jung wants.
Toby.
