Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 61911 invoked from network); 28 Apr 2006 10:32:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 28 Apr 2006 10:32:46 -0000 Received: (qmail 75084 invoked by uid 500); 28 Apr 2006 10:32:27 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 74910 invoked by uid 500); 28 Apr 2006 10:32:26 -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 74892 invoked by uid 99); 28 Apr 2006 10:32:26 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Apr 2006 03:32:26 -0700 X-ASF-Spam-Status: No, hits=1.3 required=10.0 tests=HTML_MESSAGE,RCVD_IN_BL_SPAMCOP_NET,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of man.geronimo@gmail.com designates 64.233.182.185 as permitted sender) Received: from [64.233.182.185] (HELO nproxy.gmail.com) (64.233.182.185) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Apr 2006 03:32:25 -0700 Received: by nproxy.gmail.com with SMTP id m19so1601929nfc for ; Fri, 28 Apr 2006 03:32:04 -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=EqBASioLgUK3ib2GjjJYhljGlQ1aAojBvjo1rZ0MDdF0hbxyjgZZfbAjZHOt6fAcb2VQZ2JJFIvias9BJgLcOYXtij0slPrZmQXybEs5us4NBjFaFUdPrRO1xtTu8vzWqzYlRV7k/er9GlUaNXPsWzDhowGc7n7yEsSQfrac4xY= Received: by 10.49.9.8 with SMTP id m8mr2241745nfi; Fri, 28 Apr 2006 03:32:03 -0700 (PDT) Received: by 10.49.9.6 with HTTP; Fri, 28 Apr 2006 03:32:03 -0700 (PDT) Message-ID: <4be97fbd0604280332o28a568a1s422554f395c60992@mail.gmail.com> Date: Fri, 28 Apr 2006 16:02:03 +0530 From: Man To: dev@geronimo.apache.org Subject: Re: [jira] Updated: (GERONIMO-1431) Make deploy tool and hot deploy directory work better together In-Reply-To: <10252868.1146157478351.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_117287_25717485.1146220323638" References: <1812360184.1136734721472.JavaMail.jira@ajax.apache.org> <10252868.1146157478351.JavaMail.jira@brutus> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_117287_25717485.1146220323638 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I had sumitted a patch , that address a similar issue. Infact i remember Aaron adviced me to submit the patch for this. Actual Issue : If a application module is already deployed , and somebody tries to hot deploy , the same application , server use to throw an error and still keep the module in hot deploy directory . Patch : The patch was for deleting the application module from hot deploy directory for above issue . Probably I think , this is what in real scenari= o the server has to do. Tha patch is available with JIRA 1813 With thanks, Mansoor On 4/27/06, Aaron Mulder (JIRA) wrote: > > [ http://issues.apache.org/jira/browse/GERONIMO-1431?page=3Dall ] > > Aaron Mulder updated GERONIMO-1431: > ----------------------------------- > > Fix Version: 1.1 > (was: 1.2) > Assign To: Aaron Mulder > Priority: Critical (was: Major) > > > Make deploy tool and hot deploy directory work better together > > -------------------------------------------------------------- > > > > Key: GERONIMO-1431 > > URL: http://issues.apache.org/jira/browse/GERONIMO-1431 > > Project: Geronimo > > Type: Improvement > > Security: public(Regular issues) > > Components: deployment, Hot Deploy Dir > > Versions: 1.0 > > Reporter: Aaron Mulder > > Assignee: Aaron Mulder > > Priority: Critical > > Fix For: 1.1 > > > > > Right now if you deploy something with the deploy tool and then drop an > update in the hot deploy directory, it doesn't work. The hot deploy dir > expects you to only use the hot dpeloy dir for that module. > > Likewise, if you deploy something with the hot deploy dir and then > undeploy it with the deploy tool, it is not deleted from the hot deploy d= ir. > > Both of those can be fixed. > > -- > This message is automatically generated by JIRA. > - > If you think it was sent incorrectly contact one of the administrators: > http://issues.apache.org/jira/secure/Administrators.jspa > - > For more information on JIRA, see: > http://www.atlassian.com/software/jira > > ------=_Part_117287_25717485.1146220323638 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
I had sumitted a patch , that address a similar issue. Infac= t i remember Aaron adviced me to submit the patch for this.&= nbsp;
 
Actual Issue : If a application module is already deployed , and = somebody tries to hot deploy , the same application , server use to throw a= n error and still keep the module in hot deploy directory .
 
Patch : The patch was for deleting the application module from hot dep= loy directory for above issue . Probably I think , this is what i= n real scenario the server has to do.
 
Tha patch is available with JIRA 1813
 
With thanks,
Mansoor
 
 

 
On 4/27/06, = Aaron Mulder (JIRA) <dev@= geronimo.apache.org> wrote:
    [ http://= issues.apache.org/jira/browse/GERONIMO-1431?page=3Dall ]

Aaron Mulder updated GERONIMO-1431:
----------------------= -------------

   Fix Version: 1.1
   &nb= sp;            =     (was: 1.2)
     Assign To: A= aron Mulder
      Priority: Critical =  (was: Major)

> Make deploy tool and hot deploy directory work better together=
> --------------------------------------------------------------
= >
>          Key= : GERONIMO-1431
>        &nbs= p; URL: http://issues.apache.org/jira/browse/GERONIMO-1431
>  &= nbsp;   Project: Geronimo
>    &nb= sp;    Type: Improvement
>     Sec= urity: public(Regular issues)
>   Components: deployment, H= ot Deploy Dir
>     Versions:=20 1.0
>     Reporter: Aaron Mulder
> &nb= sp;   Assignee: Aaron Mulder
>     Prio= rity: Critical
>      Fix For: 1.1
<= br>>
> Right now if you deploy something with the deploy tool and = then drop an update in the hot deploy directory, it doesn't work. &nbs= p;The hot deploy dir expects you to only use the hot dpeloy dir for that mo= dule.
> Likewise, if you deploy something with the hot deploy dir and then= undeploy it with the deploy tool, it is not deleted from the hot deploy di= r.
> Both of those can be fixed.

--
This message is automat= ically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administra= tors:
  http://issues.apache.org/jira/secure/Administrators.jspa=
-
For more information on JIRA, see:
  http://www.atlassian.com/software/jira

------=_Part_117287_25717485.1146220323638--