Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 54103 invoked from network); 5 Apr 2006 13:37:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 5 Apr 2006 13:37:56 -0000 Received: (qmail 60215 invoked by uid 500); 5 Apr 2006 13:37:51 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 60137 invoked by uid 500); 5 Apr 2006 13:37:51 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 60119 invoked by uid 99); 5 Apr 2006 13:37:50 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Apr 2006 06:37:50 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of man.geronimo@gmail.com designates 64.233.182.186 as permitted sender) Received: from [64.233.182.186] (HELO nproxy.gmail.com) (64.233.182.186) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Apr 2006 06:37:50 -0700 Received: by nproxy.gmail.com with SMTP id l36so1020629nfa for ; Wed, 05 Apr 2006 06:37:28 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=KoLOgGHGk2OXXctUvtOLgFz3YomMubjaJsbgrEHa3GuVONoAVjPLZKq/jleW4Gy9tDIheweY1UxDNFRwUNL56XZH+SRsUkqnkLixwGe3JGy4cqhCwoMum1OeH93rzKKBL2zrLKka9rNW4Zmn3kXeBOcO1JrfOKBG2rM52YvUc3w= Received: by 10.49.81.11 with SMTP id i11mr1412563nfl; Wed, 05 Apr 2006 06:37:28 -0700 (PDT) Received: by 10.49.9.6 with HTTP; Wed, 5 Apr 2006 06:37:28 -0700 (PDT) Message-ID: <4be97fbd0604050637h13238b2bjc6db70c5bcc303f8@mail.gmail.com> Date: Wed, 5 Apr 2006 19:07:28 +0530 From: Mansoor To: dev@geronimo.apache.org Subject: Re: When already deployed application is hot deployed once gain , Server doesn't delete the module from hot deployed directory. In-Reply-To: <74e15baa0604050618k2088afc3o52e975cd46d2485d@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_54342_1786853.1144244248710" References: <4be97fbd0604050234k516d61b6m8c6c63c0646d330a@mail.gmail.com> <74e15baa0604050618k2088afc3o52e975cd46d2485d@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_54342_1786853.1144244248710 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Thanks Aaron for your prompt response , I was thinking , whether we can put this feature into our geronimo. Infact i have written a piece of code , that removes this problem.should i need to raise a jira and submit as a patch ? On 4/5/06, Aaron Mulder wrote: > > OK. For now, we recommend that you only use one deployment method on > any given application -- always use the hot deploy dir, or always use > the command-line deploy tool, etc. It's definitely possible to > confuse things at the moment by switching techniques for the same > application or module. > > Thanks, > Aaron > > On 4/5/06, lak n wrote: > > > > > > Hot deployment Issue : > > When already an application module say (hello.war) is deployed > (either > > by using manually or hot deploy procedure ) , And when some one try to > hot > > deploy the same application with same or different name ( say hello.war= | > > hello2.war | hello2 directory ) , the server throws an exception sayin= g > > there exists already an application deployed , But doesn't delete the > module > > ( hello.war | hello2.war | hello2 directory) from hot deploy director= y > > thus the next time the server starts , it tries to deploy the same > module > > once again. > > > > I think the better option in this case would be to delete the > > unsuccessfully hot deployed application file or directory from hot > deploy > > directory and show some message. > > > > With Thanks and Regards, > > Mansoor > ------=_Part_54342_1786853.1144244248710 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
Thanks Aaron for your prompt response ,
 
I was thinking , whether we can put this feature into our geronim= o.
Infact i have written a piece of code , that removes this problem.shou= ld i need to raise a jira and submit as a patch ?
 
 

 
On 4/5/06, A= aron Mulder <ammuld= er@alumni.princeton.edu> wrote:
OK.  For now, we recom= mend that you only use one deployment method on
any given application --= always use the hot deploy dir, or always use
the command-line deploy tool, etc.  It's definitely possible = to
confuse things at the moment by switching techniques for the same
= application or module.

Thanks,
   Aaron

On 4/5/0= 6, lak n < man.geronimo@gmail.com> wrote:
>
>
> Hot deploymen= t Issue :
>     When already an application modul= e say (hello.war) is deployed (either
> by using manually or hot depl= oy procedure ) , And when some one try to hot
> deploy the same application with same or different name ( say hell= o.war |
> hello2.war | hello2 directory ) ,  the server thr= ows an exception saying
> there exists already an application deploye= d , But doesn't delete the module
> ( hello.war | hello2.war |  hello2 directory)  = ;from hot deploy directory
> thus the next time the server starts , i= t tries to deploy the same module
> once again.
>
> =    I think the better option in this case would be to delete= the
> unsuccessfully hot deployed application file or directory from hot= deploy
> directory and show some message.
>
> With Thank= s and Regards,
> Mansoor

------=_Part_54342_1786853.1144244248710--