Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 98705 invoked from network); 24 Oct 2005 14:44:50 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 24 Oct 2005 14:44:50 -0000 Received: (qmail 99264 invoked by uid 500); 24 Oct 2005 14:44:45 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 99214 invoked by uid 500); 24 Oct 2005 14:44:44 -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 99199 invoked by uid 99); 24 Oct 2005 14:44:44 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from [167.206.4.205] (HELO mta10.srv.hcvlny.cv.net) (167.206.4.205) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Oct 2005 07:44:44 -0700 Received: from [10.0.1.5] (ool-43560634.dyn.optonline.net [67.86.6.52]) by mta10.srv.hcvlny.cv.net (Sun Java System Messaging Server 6.2-2.06 (built May 11 2005)) with ESMTP id <0IOV00FXECX6SLOR@mta10.srv.hcvlny.cv.net> for dev@geronimo.apache.org; Mon, 24 Oct 2005 10:43:55 -0400 (EDT) Date: Mon, 24 Oct 2005 10:43:53 -0400 From: "Geir Magnusson Jr." Subject: Re: The autodeploy feature in Geronimo In-reply-to: <435CECC3.4040707@gmail.com> To: dev@geronimo.apache.org Message-id: <9E0E38DF-BC7C-4FAB-AAFC-EB824273F13B@apache.org> MIME-version: 1.0 X-Mailer: Apple Mail (2.734) Content-type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Content-transfer-encoding: 7BIT References: <435BEDB5.5070008@apache.org> <435C069E.4000503@gmail.com> <435C07E7.1030301@savoirtech.com> <435CECC3.4040707@gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N I said the same thing, but my message never made it. :/ I think you'd want to leave the file there, because then you can examine it to see what exactly you deployed... You could also take that exact artifact and give to someone else for deployment elsewhere (in QA, for example) confident that what you tested is what you gave out. geir On Oct 24, 2005, at 10:16 AM, Sachin Patel wrote: > > > Jeff Genender wrote: > >> Sachin Patel wrote: >> >>> >>> >>> Jacek Laskowski wrote: >>> >>> Am I right that the simplest solution is to develop a GBean that >>> >>> >>>> would monitor a directory and hand over a deployable to a deployer? >>>> >>> >>> >>> This was my thinking as well. The directory would listen for >>> adds, modifications, and deletions. >>> >> I think this may be somewhat confusing. I think when dropping in >> the directory, it should should deploy...then be immediately >> removed from the directory. IMHO, this dir should be for hot >> deploy only. Let the deployer decide if it should be updated or >> added. I think the deletions should not be done through this >> dir. We should use the normal undeploy capabilities of the deployer. >> > > Wouldn't it be more confusing to the user if their file got removed > after it got deployed? I feel the point of a "live" directory is > for the runtime to be able to react to any changes to it, including > deletions. Both Jboss and Websphere's hot deploy capability allow > deletions. > > What does tomcat allow? > > Sachin > > >>> >>> >>>> >>>> Jacek >>>> > -- Geir Magnusson Jr +1-203-665-6437 geirm@apache.org