geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Srihari S" <>
Subject RE: J2EE DeploymentManager ( was J2EE deployment verifier)
Date Wed, 13 Aug 2003 13:43:06 GMT
Hi All
  When I was going thru the deployment api spec I thought it would be good
to bring up some points:

>From a preliminary reading of the spec i saw there are no apis explicitly
designed to do the verification
of a deployable unit. From this I infer that the verifier can be an internal
module which could be used
by the deploy tool. So we could go full steam on its design and
implementation. In this regard I am trying to
jot the list of checks that our verifier will have to do (This is mentioned
in the j2ee specs).
So in a way it will be equivalent to arriving at requirement specs for the
With the list of dos and donts that a verifier has to achieve we could go
abt with design.Also the design of
ant hooks can be taken care.Can we??

Next is something abt the big picture. Certainly the verifer is a small part
of the deployment process.
But to achieve compliance we will have to implement the deployment spec as a
whole. Has anyone given
thought to this issue?


-----Original Message-----
From: Weston M. Price []
Sent: Wednesday, August 13, 2003 1:33 AM
Subject: Re: J2EE DeploymentManager ( was J2EE deployment verifier)

No, I think splitting them up would be good....


On Tuesday 12 August 2003 11:41 pm, Jonathan Duty wrote:
> I'm creating a maven module to add to the cvs project.
> Do we want to plan on the DeploymentManager, VerificationEngine, and
> DeploymentEngine being in one module?
> What do you all think?
> ~Jonathan
> Weston M. Price wrote:
> >Just thought I should start a new thread....
> >
> >My KMail was getting dominated!
> >
> >Weston

View raw message