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" <[EMAIL PROTECTED]> Date: Wed, 13 Aug 2003 09:48:26 +0000 To: [EMAIL PROTECTED] 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:[EMAIL PROTECTED] > > Sent: Wednesday, August 13, 2003 9:43 AM > > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > > 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:[EMAIL PROTECTED] > > Sent: Wednesday, August 13, 2003 1:33 AM > > To: [EMAIL PROTECTED] > > 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
