geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Srihari S" <sriha...@blr.pin.philips.com>
Subject RE: J2EE DeploymentManager ( was J2EE deployment verifier)
Date Thu, 14 Aug 2003 05:03:38 GMT
Hi 'Verifier' team

I have done some ground work to arrive at a high level overview of the
verification engine.
Please look at the deployment wiki page for a draft requirements list and a
hi level system model.
http://nagoya.apache.org/wiki/apachewiki.cgi
I strongly recommend that we spend adequate time on drafting the complete
set requirements for the verifier.
Event though this module will be an internal module we still have to be
careful since it is going to be the first
line of defence for the deploy tool.


warm regards
Hari


-----Original Message-----
From: klas axell [mailto:klasaxell@linuxmail.org]
Sent: Thursday, August 14, 2003 3:35 AM
To: geronimo-dev@incubator.apache.org
Subject: Re: J2EE DeploymentManager ( was J2EE deployment verifier)


Ok, add me to that list as well. I'll start looking at that list.

/Klas

----- Original Message -----
From: "Weston M. Price" <weston_p@yahoo.com>
Date: Wed, 13 Aug 2003 16:46:00 +0000
To: geronimo-dev@incubator.apache.org
Subject: Re: J2EE DeploymentManager ( was J2EE deployment verifier)

> Yes, at present there are at least four people, that I know of anyway,
> interested in the VerificationEngine:
>
> Weston (me)
> Jonathan Duty
> Srihari S
> Denes
>
> I think you are right, we basically want to start with a list of our
> verification requirements and take it from there.
>
>
>
> Regards,
> Weston
>
> On Wednesday 13 August 2003 06:47 pm, klas axell wrote:
> > I have been reading through some of the spec today and the thing I can
> > begin working on is the verifier. I saw in another post in this thread
that
> > someone was talking about making a list (ie simplify the spec) of what
the
> > verifier has to verify. That would indeed be a good starting point. Is
> > someone working on this list of requirements?
> >
> > /Klas
> >
> > ----- Original Message -----
> > From: "Weston M. Price" <weston_p@yahoo.com>
> > Date: Wed, 13 Aug 2003 09:48:26 +0000
> > To: geronimo-dev@incubator.apache.org
> > Subject: Re: J2EE DeploymentManager ( was J2EE deployment verifier)
> >
> > > I agree with Srihari in that the Verification manager does not have to
> > > implement the spec interfaces, however, the DeploymentManager does,
this
> > > would be where we would implment DDRoot, DDConfig etc.....in some ways
> > > the DeploymentManager would just use the services of the
> > > VerificatinoEngine as one step in the process of actual deployment.
> > >
> > > Is this in line with what you guys were thinking?
> > >
> > > On Wednesday 13 August 2003 01:52 pm, Jonathan Duty wrote:
> > > > When we implement this module, we could actually implement it to
> > > > exactly follow the API specs (JSR 88).  That means implementing the
> > > > DeploymentManager interface on top of it and such.  That way any
> > > > application (ant, Eclipse, etc) that is equipped to deploy packages
> > > > could interface with it.  It would just fall short of actually
> > > > communicating with MBeans and deploying the package.
> > > >
> > > > When this module is used internally (within the REAL deployment
> > > > manager) it could just bypass or override the Verification's
Deployment
> > > > manager.
> > > >
> > > > ~Jonathan
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: Srihari S [mailto:sriharis@blr.pin.philips.com]
> > > > Sent: Wednesday, August 13, 2003 9:43 AM
> > > > To: geronimo-dev@incubator.apache.org; weston_p@yahoo.com
> > > > Subject: RE: J2EE DeploymentManager ( was J2EE deployment verifier)
> > > >
> > > > 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
> > > > verifier.
> > > > 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?
> > > >
> > > > regards
> > > > Hari
> > > >
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: Weston M. Price [mailto:weston_p@yahoo.com]
> > > > Sent: Wednesday, August 13, 2003 1:33 AM
> > > > To: geronimo-dev@incubator.apache.org
> > > > Subject: Re: J2EE DeploymentManager ( was J2EE deployment verifier)
> > > >
> > > >
> > > > No, I think splitting them up would be good....
> > > >
> > > > Weston
> > > >
> > > > 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

--
______________________________________________
http://www.linuxmail.org/
Now with e-mail forwarding for only US$5.95/yr

Powered by Outblaze


Mime
View raw message