You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Aaron Mulder <am...@alumni.princeton.edu> on 2005/11/10 09:04:24 UTC
Hot Deploy...
...now works if you copy your module JAR into geronimo/deploy/ -- let
me know how it goes. :)
Aaron
P.S. You can adjust the directory and frequency in config.xml:
<gbean name="HotDeployer">
<attribute name="path">deploy</attribute>
<attribute name="pollIntervalMillis">2000</attribute>
</gbean>
Re: Hot Deploy...
Posted by Jacek Laskowski <jl...@apache.org>.
Aaron Mulder wrote:
> ...now works if you copy your module JAR into geronimo/deploy/ -- let
> me know how it goes. :)
Excellent! I was myself thinking about it for a while, but got
completely swamped with PetStore and the security configuration of it I
can't understand at all :( It's nice to have it at last.
> Aaron
Jacek
Re: Hot Deploy...
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
On 11/10/05, Joe Bohn <jo...@earthlink.net> wrote:
> Yes, I figured it defaulted to one of the containers ... the question
> was "how does it choose" and can it be overridden? For applications
> like the web console which has two instances deployed this is kind of
> important to understand. :-)
It chooses based on the namespace in the geronimo-web.xml, and if that
uses the generic namespace, it chooses based on a property set on one
of the deployment GBeans that says what the default web deployer is (I
forget which one, but djencks would know or you can look in
config.xml). The behavior there is 100% identical to if you deploy
with the deploy tool (either way, something has to figure which web
container to use).
Aaron
Re: Hot Deploy...
Posted by Joe Bohn <jo...@earthlink.net>.
Sachin Patel wrote:
> Joe Bohn wrote:
>
>>
>> Aaron Mulder wrote:
>>
>>> ...now works if you copy your module JAR into geronimo/deploy/ -- let
>>> me know how it goes. :)
>>>
>>> Aaron
>>>
>>> P.S. You can adjust the directory and frequency in config.xml:
>>> <gbean name="HotDeployer">
>>> <attribute name="path">deploy</attribute>
>>> <attribute name="pollIntervalMillis">2000</attribute>
>>> </gbean>
>>>
>>
>> but is there any way to target a specific container at deploy time
>> when the dependency is generic?
>
> The whole intent of hot deploy is so you don't have to think about and
> have to specify these things during deployment. You just drop it in and
> pray. Default everything you can.
>
Yes, I figured it defaulted to one of the containers ... the question
was "how does it choose" and can it be overridden? For applications
like the web console which has two instances deployed this is kind of
important to understand. :-)
>>
>> Also, how do you specify a plan that is external from the archive?
>
> You can't. (at least not now). Plan needs to contained within the archive.
>
>
Ok, that's what I suspected.
--
Joe Bohn
joe.bohn@earthlink.net
"He is no fool who gives what he cannot keep, to gain what he cannot
lose." -- Jim Elliot
Re: Hot Deploy...
Posted by Sachin Patel <sp...@gmail.com>.
Joe Bohn wrote:
>
> Aaron Mulder wrote:
>> ...now works if you copy your module JAR into geronimo/deploy/ -- let
>> me know how it goes. :)
>>
>> Aaron
>>
>> P.S. You can adjust the directory and frequency in config.xml:
>> <gbean name="HotDeployer">
>> <attribute name="path">deploy</attribute>
>> <attribute name="pollIntervalMillis">2000</attribute>
>> </gbean>
>>
>
> but is there any way to target a specific container at deploy time
> when the dependency is generic?
The whole intent of hot deploy is so you don't have to think about and
have to specify these things during deployment. You just drop it in and
pray. Default everything you can.
>
> Also, how do you specify a plan that is external from the archive?
You can't. (at least not now). Plan needs to contained within the archive.
Re: Hot Deploy...
Posted by Joe Bohn <jo...@earthlink.net>.
Aaron Mulder wrote:
> ...now works if you copy your module JAR into geronimo/deploy/ -- let
> me know how it goes. :)
>
> Aaron
>
> P.S. You can adjust the directory and frequency in config.xml:
> <gbean name="HotDeployer">
> <attribute name="path">deploy</attribute>
> <attribute name="pollIntervalMillis">2000</attribute>
> </gbean>
>
If there are multiple web managers/containers running then how does the
Hot Deploy (or Deployment Manager) decide which will be the target
container? I assume it would honor a dependency in the plan for a
specific container ... but is there any way to target a specific
container at deploy time when the dependency is generic?
Also, how do you specify a plan that is external from the archive?
--
Joe Bohn
joe.bohn@earthlink.net
"He is no fool who gives what he cannot keep, to gain what he cannot
lose." -- Jim Elliot
Re: Hot Deploy...
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
Yes
Aaron
On 11/10/05, Sachin Patel <sp...@gmail.com> wrote:
> Awesome! Does it handle re/un-deploy's?
>
> Aaron Mulder wrote:
> > ...now works if you copy your module JAR into geronimo/deploy/ -- let
> > me know how it goes. :)
> >
> > Aaron
> >
> > P.S. You can adjust the directory and frequency in config.xml:
> > <gbean name="HotDeployer">
> > <attribute name="path">deploy</attribute>
> > <attribute name="pollIntervalMillis">2000</attribute>
> > </gbean>
> >
> >
>
>
Re: Hot Deploy...
Posted by Sachin Patel <sp...@gmail.com>.
Nevermind, looked at the source changes, looks like it does :)
Sachin Patel wrote:
> Awesome! Does it handle re/un-deploy's?
>
> Aaron Mulder wrote:
>> ...now works if you copy your module JAR into geronimo/deploy/ -- let
>> me know how it goes. :)
>>
>> Aaron
>>
>> P.S. You can adjust the directory and frequency in config.xml:
>> <gbean name="HotDeployer">
>> <attribute name="path">deploy</attribute>
>> <attribute name="pollIntervalMillis">2000</attribute>
>> </gbean>
>>
>>
>
>
Re: Hot Deploy...
Posted by Sachin Patel <sp...@gmail.com>.
Awesome! Does it handle re/un-deploy's?
Aaron Mulder wrote:
> ...now works if you copy your module JAR into geronimo/deploy/ -- let
> me know how it goes. :)
>
> Aaron
>
> P.S. You can adjust the directory and frequency in config.xml:
> <gbean name="HotDeployer">
> <attribute name="path">deploy</attribute>
> <attribute name="pollIntervalMillis">2000</attribute>
> </gbean>
>
>