Mailing-List: contact user-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: domain of linsun.unc@gmail.com designates
 64.233.184.231 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:from:to:subject:date:message-id:mime-version:content-type:content-transfer-encoding:x-priority:x-msmail-priority:x-mailer:x-mimeole:importance:in-reply-to;
        b=Fxpxsfmn+DJAYOct94crwaLZsB+GwXCON8qfD07FDFP8JegGxRhrG6g3DJ30AwJ+X0yYSLysqmKV28UVnmts1bsMxpi6TrevOgRODbm/8YSn5BDzYl1SUtIWdcosHlkjsNCIRwjVY/DiegPv6sXtVMToWoZ/27PJluzPpKgvzJg=
From: "Lin Sun" <linsun.unc@gmail.com>
To: <user@geronimo.apache.org>
Subject: RE: in-place deployment
Date: Wed, 14 Jun 2006 11:13:06 -0400
Message-ID: <004f01c68fc5$0a561220$24ef4109@raleigh.ibm.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Importance: Normal
In-Reply-To: <B8483022-7E4C-4935-9400-9094889D3972@gmail.com>

I could not get it work with .war file either.   But I do see David Jencks
gave the following as an example in his article (see link below):

java -jar bin/deployer.jar deploy --inPlace appPerPort.ear

Maybe David got it working at one point or it just work with ear file?

Lin

-----Original Message-----
From: Sachin Patel [mailto:sppatel@gmail.com] On Behalf Of Sachin Patel
Sent: Wednesday, June 14, 2006 9:11 AM
To: user@geronimo.apache.org
Subject: Re: in-place deployment

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 <linsun.unc@gmail.com> 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