jonathan...i am unclear on a couple of points: 1. "When we implement this module, we could actually implement it to exactly follow the API specs (JSR 88)" I hope "this module" means the verification module.
2. "That means implementing the DeploymentManager interface on top of it and such" So if i am right you want an independent Verification module first but at the same time we create a **pseudo??** DeploymentManager implementation which will enable ant etc to hook onto it immediately. Yes such a thing would ceratinly fall short of communicating with the MBeans. Nevertheless the advantage would be that we are on the track implementing the deployment spec from the word go and this small wonder of ours would have successfully made itself indispensable to the sucessful impl of the deployment spec. Which i guess is a win-win situation!! I hope i understand u correctly -----Original Message----- From: Jonathan Duty [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 13, 2003 7:22 PM To: [EMAIL PROTECTED] Subject: RE: J2EE DeploymentManager ( was J2EE deployment verifier) 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
