Return-Path: Delivered-To: apmail-geronimo-user-archive@www.apache.org Received: (qmail 77887 invoked from network); 14 Jun 2006 13:11:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 14 Jun 2006 13:11:39 -0000 Received: (qmail 10022 invoked by uid 500); 14 Jun 2006 13:11:37 -0000 Delivered-To: apmail-geronimo-user-archive@geronimo.apache.org Received: (qmail 9676 invoked by uid 500); 14 Jun 2006 13:11:35 -0000 Mailing-List: contact user-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: user@geronimo.apache.org List-Id: Delivered-To: mailing list user@geronimo.apache.org Received: (qmail 9658 invoked by uid 99); 14 Jun 2006 13:11:35 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Jun 2006 06:11:35 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=RCVD_IN_SORBS_WEB,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of sppatel@gmail.com designates 64.233.184.224 as permitted sender) Received: from [64.233.184.224] (HELO wr-out-0506.google.com) (64.233.184.224) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Jun 2006 06:11:34 -0700 Received: by wr-out-0506.google.com with SMTP id i2so71739wra for ; Wed, 14 Jun 2006 06:11:13 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:mime-version:in-reply-to:references:content-type:message-id:content-transfer-encoding:from:subject:date:to:x-mailer:sender; b=VdBwWAl6esOvT/MQUwk6WInHNn1Qxm4I1wLRGZpbpXFyNuMTpkMHFGBx+eV8zv32etBPO7L12ivO3fKNPjvCKOhBUCvXok1khyzA9doh3Y/2qWqlOHZC4U+tobdEMTRURI+4h5q0L9AaHo94NUNmdVpQ793EB0GC7NBrGjBpzBc= Received: by 10.54.103.13 with SMTP id a13mr646673wrc; Wed, 14 Jun 2006 06:11:13 -0700 (PDT) Received: from ?9.27.41.131? ( [129.33.49.251]) by mx.gmail.com with ESMTP id g5sm341778wra.2006.06.14.06.11.13; Wed, 14 Jun 2006 06:11:13 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v750) In-Reply-To: <44900526.5070606@optusnet.com.au> References: <002b01c68f1d$97f44730$24ef4109@raleigh.ibm.com> <44900526.5070606@optusnet.com.au> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Sachin Patel Subject: Re: in-place deployment Date: Wed, 14 Jun 2006 09:11:11 -0400 To: user@geronimo.apache.org X-Mailer: Apple Mail (2.750) Sender: Sachin Patel X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N It should probably be release-noted that in-place deployment does not work with stand-alone ejb jars. (At least the last time I tried it failed). So it may very well be that it only works for stand- alone .wars or ears containing only web modules. On Jun 14, 2006, at 8:46 AM, Gianny Damour wrote: > Hi Lin, > > I just checked and you can do: > $ java -jar bin/deployer.jar help distribute > > Command-line deployer syntax: > deployer [general options] command [command options] > > Help for command: distribute > > deployer distribute [--inPlace] [--targets target;target;...] > [module] [plan] > > <...> > > If inPlace is provided, the module is not copied to the > configuration store of the selected targets. The targets > directly use the module. > > > The help for the deploy command identifies the --inPlace flag but > does not provide a description for it. > > Thanks, > Gianny > > > Lin Sun wrote: > >> Thanks. I executed deploy.bat but didn't see the -inPlace option >> from the >> help menu. Should we add this option to the output of executing >> deploy.bat? >> >> Then I saw David Jenck's article >> (http://opensource.atlassian.com/confluence/oss/display/GERONIMO/ >> Exposing+We >> b+Applications+on+distinct+ports), so I figured out I can just call >> "deploy.bat deploy --inPlace" to use it. What I found out is if I >> execute: >> >> deploy.bat deploy --inPlace path\hello.war >> >> I got the following error: >> Error: Unable to distribute hello-1.1.war: In place deployment is >> not allowed for packed module >> >> Then I tried: >> deploy.bat deploy --inPlace path\hello >> and it worked well. I did see David used an ear file as the last >> parameter >> in the example given in the article... >> >> Lin >> >> >> >> -----Original Message----- >> From: ammulder@gmail.com [mailto:ammulder@gmail.com] On Behalf Of >> Aaron >> Mulder >> Sent: Tuesday, June 13, 2006 2:42 PM >> To: dev@geronimo.apache.org >> Subject: Re: RELEASE-NOTES-1.1 >> >> On 6/13/06, Lin Sun wrote: >> >>> I am trying to learn what the in-place deployment mean and how to >>> use it. >>> My understanding was that users can update the hot deploy files (for >>> example, update one jsp file) in the Geronimo_home\deploy >>> directory and >>> server will redeploy the change automatically. This was not >>> working in >>> 1.0, as users need to replace the entire directory in the >>> Geronimo_home\deploy directory. >>> >> >> That should be true in both 1.0 and 1.1 (if not, I guess it's a bug). >> >> But in 1.1, there is a separate option, which is to not copy your >> files to the hot deploy directory at all, but instead use the deploy >> tool with a special option to enable an in-place deployment. This >> means that instead of copying your files into the server directory at >> all, it will deploy and access them from wherever they currently are. >> >> Thanks, >> Aaron >> >> >>> But after reading your note below, I think I am lost. Please >>> advise. >>> >>> Lin >>> >>> -----Original Message----- >>> From: ammulder@gmail.com [mailto:ammulder@gmail.com] On Behalf Of >>> Aaron >>> Mulder >>> Sent: Thursday, June 08, 2006 7:23 PM >>> To: dev@geronimo.apache.org >>> Subject: Re: RELEASE-NOTES-1.1 >>> >>> - We should add a point about in-place deployment. "Geronimo >>> supports in-place deployment, which means an archive or directory >>> can >>> be deployed without being copied into the Geronimo directory tree." >>> >>> >>> >>> >>> >> >> >> >> >> > > -sachin