Scott 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?
Count me in.
"Castro, David" wrote:
> >
> > 3. Puts all of the ejb-jars in the application classpath.
> > As I noted above, I just patched Installer so that this no longer
> > happens!! 2 Reasons:
> > A. It introduces a bug if there are multiple jaws-managed beans
Could the root cause of the problem be a jaws bug, then?
I'm just asking.
> > B. It doesnt make any sense!! Yes, I know that J2EE RI does it
> > this way, but there is nothing in the spec to indicate (or even suggest)
> > that it should be done this way, and I regard the RI behavior as a bug.
> >
I think it makes a lot of sense. The deployment occurs within the
context of an application, and by definition (if not by the spec)
application components share resources.
The vision embodied in JPS 1.1.1 is an application development model
where jsp pages, custom tag libraries, JavaBeans and Ejb's all have
unique application roles to play. From this perspective, the current
state of the Deployer is a limiting factor.
JPS may not be the "acid" test of the J2EE spec, but it's a pretty
good one.
Tom
