Return-Path: Delivered-To: apmail-incubator-geronimo-dev-archive@incubator.apache.org Received: (qmail 93041 invoked by uid 500); 11 Aug 2003 14:36:30 -0000 Mailing-List: contact geronimo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: geronimo-dev@incubator.apache.org Delivered-To: mailing list geronimo-dev@incubator.apache.org Received: (qmail 92954 invoked from network); 11 Aug 2003 14:36:28 -0000 Received: from gw-us1.philips.com (63.114.235.94) by daedalus.apache.org with SMTP; 11 Aug 2003 14:36:28 -0000 Received: from smtpscan-us1.philips.com (smtpscan-us1.philips.com [167.81.233.25]) by gw-us1.philips.com (Postfix) with ESMTP id A9D8E58D4F for ; Mon, 11 Aug 2003 09:36:30 -0500 (CDT) Received: from smtpscan-us1.philips.com (localhost [127.0.0.1]) by localhost.philips.com (Postfix) with ESMTP id 4A83519C4C for ; Mon, 11 Aug 2003 09:36:30 -0500 (CDT) Received: from smtprelay-hk1.philips.com (smtprelay-asp1.philips.com [130.147.65.5]) by smtpscan-us1.philips.com (Postfix) with ESMTP id 1ECA819C47 for ; Mon, 11 Aug 2003 09:36:29 -0500 (CDT) Received: from indpsc01.blr.pin.philips.com (indpsc01.blr.pin.philips.com [161.85.26.5]) by smtprelay-hk1.philips.com (8.9.3-p1/8.8.5-1.2.2m-19990317) with ESMTP id WAA05131 for ; Mon, 11 Aug 2003 22:36:26 +0800 (HKT) Received: from coxxx050 (pbe113.blr.pin.philips.com [161.85.22.113]) by indpsc01.blr.pin.philips.com (8.8.8+Sun/8.6.10-1.2.2a-970219) with SMTP id UAA19913 for ; Mon, 11 Aug 2003 20:06:49 GMT From: "Srihari S" To: Subject: RE: J2EE deployment verifier Date: Mon, 11 Aug 2003 20:18:56 +0530 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 In-Reply-To: <20030811142252.60282.qmail@web11002.mail.yahoo.com> X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N i still feel they can be friends...the deploy tool will do the verification as a part of the deployment process then it can use the apis that we develop. Chris, u seem to have done some homework on the deployment apis..can u throw some light on what it says w.r.t the verification process -----Original Message----- From: Chris Opacki [mailto:chris_opacki@yahoo.com] Sent: Monday, August 11, 2003 7:53 PM To: geronimo-dev@incubator.apache.org Subject: RE: J2EE deployment verifier My bad...I was assuming the deploy tool and the verifier would be close friends. ;) --- Srihari S wrote: > True > Our module is just going to check and declare > whether or not a given unit of > deployment > is deployable on a j2ee server or not. > > Nothing more..nothing less. > Building this unit will be our mission..right > weston?? > > -----Original Message----- > From: Weston M. Price [mailto:weston_p@yahoo.com] > Sent: Monday, August 11, 2003 3:05 PM > To: geronimo-dev@incubator.apache.org > Subject: Re: J2EE deployment verifier > > > And even further, let's clarify the verification is > a completely different > animal than actual deployment. Am I correct on this > one at least in terms of > the way we are thinking about this module? > > Weston > > On Monday 11 August 2003 01:50 pm, Srihari S wrote: > > just a clarification..i hope ur referring to j2ee > 1.4 spec > > lets have a common understanding on this...u cud > specify the correct > > version > > > > -----Original Message----- > > From: Chris Opacki [mailto:chris_opacki@yahoo.com] > > Sent: Monday, August 11, 2003 7:02 PM > > To: geronimo-dev@incubator.apache.org; > weston_p@yahoo.com > > Subject: RE: J2EE deployment verifier > > > > > > The specs also provides a basic SPI API. It also > > provides a high level architecture describe the > > relations between deployable components and > objects in > > the deploymeny tool and manager. It's an > interesting > > read. > > > > --- Srihari S > wrote: > > > never mind ur choice of words....if we end up > using > > > the rule engine concept > > > it will because of u:) > > > So at a very hi level we can look at the > verifier as > > > > > > Input Process Output > > > > > > JAR Verify the correctness OK/NOK with error > log > > > WAR by parsing the DD > > > EAR and applying correctness > > > RAR rules > > > > > > > > > While it is true that the verifier can be a > > > standalone app and we must > > > design its internals in this spirit > > > it may also be worthwhile to decide early on how > it > > > will get into the > > > geronimo frwk > > > > > > > > > -----Original Message----- > > > From: Weston M. Price > [mailto:weston_p@yahoo.com] > > > Sent: Monday, August 11, 2003 2:04 PM > > > To: geronimo-dev@incubator.apache.org > > > Subject: Re: J2EE deployment verifier > > > > > > > > > As a modular component I think this J2EE > verifier > > > engine/processor would be > > > very useful in a number of projects; it could > even > > > be a standalone module > > > that would allow a developer to validate their > > > archive before ever even > > > trying to deploy it in a target environment. Of > > > course, you wouldn't be able > > > to see those 100+ line stack traces roll across > your > > > tty when you go to > > > deploy your archive; that would be the one > > > drawback.... > > > > > > Regards, > > > > > > Weston > > > > > > On Monday 11 August 2003 08:26 am, Weston M. > Price > > > > > > wrote: > > > > Yeah, I knew that term was going to come back > at > > > > > > me, poor choice of words > > > > > > > on my part. I was basically thinking in terms > of > > > > > > "rules" as conditions > > > that > > > > > > > need to be satisfied to fulfill a deployment; > not > > > > > > in terms of a full blown > > > > > > > rules engine (though this would be somewhat > > > > > > interesting). At the very core > > > > > > > what you really have is a set of conditions > that > > > > > > when applied to a > > > > > > > deployable unit (EAR, WAR, SAR etc) must be > met > > > > > > for the archive to be > > > > > > > deployed. A verifier exists as sort of a > watchdog > > > > > > that prevents archives > > > > > > > from violating a discreet set of constraints. > > > > > > > > Regards, > > > > > > > > Weston > > > > > > > > On Monday 11 August 2003 12:36 pm, Srihari S > > > > > > wrote: > > > > > i did not have this rule engine picture when > i > > > > > > started thinking abt this > > > > > > > > verifier.. > > > > > ru looking at the design of some open src > rule > > > > > > engines for designing > > > this > > > > > > > > verifier? > > > > > > > > > > -----Original Message----- > > > > > From: Weston M. Price > > > > > > [mailto:weston_p@yahoo.com] > > > > > > > > Sent: Monday, August 11, 2003 12:12 PM > > > > > To: Srihari S; > geronimo-dev@incubator.apache.org > > > > > Subject: Re: J2EE deployment verifier > > > > > > > > > > > > > > > It's an interesting subject for a few > reasons: > > > > > What we are really talking about is a type > of > > > > > > rules engine where > > > certain > > > > > > > > conditions have to be met to achieve a > > > > > > successful "deployment". The most > > > > > > > > intriguing aspect, at least to me, would be > to > > > > > > make this module > > > > > > > > extensible and "forward looking" because we > all > > > > > > know that specifications > > > > > > > > are static and never change right? :-) As > > > > > > Geronimo grows with J2EE (and > === message truncated === __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com