You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Ted Kirby <te...@gmail.com> on 2007/08/08 02:14:36 UTC
proper behavior for "deploy list-targets" with multiple repositories when server is not running
When the server is running, the list-targets command lists additional
repositories that may have been configured. When the server is not
running, only the base repository is listed.
What should the correct behavior be?
The list of repositories are kept in config.xml and are not available
remotely when the server is not running. It seems nothing should be
returned by list-targets when the server is down.
Re: proper behavior for "deploy list-targets" with multiple repositories
when server is not running
Posted by Donald Woods <dw...@apache.org>.
One scenario, would be with running multiple server instances, where each
instance gets a unique config-store/repo...
Another twist on the same scenario, would be installing the server as root and
locking down the files so users couldn't change the base server install, but
would create their own instance under their home dir which uses the shared
server files....
-Donald
David Jencks wrote:
>
> On Aug 7, 2007, at 8:01 PM, Donald Woods wrote:
>
>> Hmmm... sounds like we need an Admin Portlet to add/remove additional
>> config-stores, so they get registered in both config.xml and
>> offline-deployer-config.xml at the same time....
>
> That seems like it's probably a good idea.... are there cases where you
> would want the offline deployer to know about a different set of
> config-stores than the server? At first I thought perhaps a farm
> situation might be one but I'd expect such a setup to share the app
> deployment in the main config-store and configure each app in the
> server's individual config.xml's
>
> thanks
> david jencks
>
>>
>>
>> -Donald
>>
>>
>> David Jencks wrote:
>>> On Aug 7, 2007, at 5:14 PM, Ted Kirby wrote:
>>>> When the server is running, the list-targets command lists additional
>>>> repositories that may have been configured. When the server is not
>>>> running, only the base repository is listed.
>>>>
>>>> What should the correct behavior be?
>>>>
>>>> The list of repositories are kept in config.xml and are not available
>>>> remotely when the server is not running. It seems nothing should be
>>>> returned by list-targets when the server is down.
>>> I don't think that's quite right. Isn't the list always that of the
>>> set of config-stores running in the relevant kernel, which for the
>>> offline deployer is typically just the "main" config-store? I think
>>> if you want to have the offline deployer deploy to more config-stores
>>> you can add configurations that start those config stores to the
>>> offline-deployer-config.xml
>>> I think the current behavior is fine.
>>> thanks
>>> david jencks
>
>
>
Re: proper behavior for "deploy list-targets" with multiple repositories when server is not running
Posted by David Jencks <da...@yahoo.com>.
On Aug 7, 2007, at 8:01 PM, Donald Woods wrote:
> Hmmm... sounds like we need an Admin Portlet to add/remove
> additional config-stores, so they get registered in both config.xml
> and offline-deployer-config.xml at the same time....
That seems like it's probably a good idea.... are there cases where
you would want the offline deployer to know about a different set of
config-stores than the server? At first I thought perhaps a farm
situation might be one but I'd expect such a setup to share the app
deployment in the main config-store and configure each app in the
server's individual config.xml's
thanks
david jencks
>
>
> -Donald
>
>
> David Jencks wrote:
>> On Aug 7, 2007, at 5:14 PM, Ted Kirby wrote:
>>> When the server is running, the list-targets command lists
>>> additional
>>> repositories that may have been configured. When the server is not
>>> running, only the base repository is listed.
>>>
>>> What should the correct behavior be?
>>>
>>> The list of repositories are kept in config.xml and are not
>>> available
>>> remotely when the server is not running. It seems nothing should be
>>> returned by list-targets when the server is down.
>> I don't think that's quite right. Isn't the list always that of
>> the set of config-stores running in the relevant kernel, which for
>> the offline deployer is typically just the "main" config-store? I
>> think if you want to have the offline deployer deploy to more
>> config-stores you can add configurations that start those config
>> stores to the offline-deployer-config.xml
>> I think the current behavior is fine.
>> thanks
>> david jencks
Re: proper behavior for "deploy list-targets" with multiple repositories
when server is not running
Posted by Donald Woods <dw...@apache.org>.
Hmmm... sounds like we need an Admin Portlet to add/remove additional
config-stores, so they get registered in both config.xml and
offline-deployer-config.xml at the same time....
-Donald
David Jencks wrote:
>
> On Aug 7, 2007, at 5:14 PM, Ted Kirby wrote:
>
>> When the server is running, the list-targets command lists additional
>> repositories that may have been configured. When the server is not
>> running, only the base repository is listed.
>>
>> What should the correct behavior be?
>>
>> The list of repositories are kept in config.xml and are not available
>> remotely when the server is not running. It seems nothing should be
>> returned by list-targets when the server is down.
>
> I don't think that's quite right. Isn't the list always that of the set
> of config-stores running in the relevant kernel, which for the offline
> deployer is typically just the "main" config-store? I think if you want
> to have the offline deployer deploy to more config-stores you can add
> configurations that start those config stores to the
> offline-deployer-config.xml
>
> I think the current behavior is fine.
>
> thanks
> david jencks
>
>
>
Re: proper behavior for "deploy list-targets" with multiple repositories when server is not running
Posted by David Jencks <da...@yahoo.com>.
On Aug 7, 2007, at 5:14 PM, Ted Kirby wrote:
> When the server is running, the list-targets command lists additional
> repositories that may have been configured. When the server is not
> running, only the base repository is listed.
>
> What should the correct behavior be?
>
> The list of repositories are kept in config.xml and are not available
> remotely when the server is not running. It seems nothing should be
> returned by list-targets when the server is down.
I don't think that's quite right. Isn't the list always that of the
set of config-stores running in the relevant kernel, which for the
offline deployer is typically just the "main" config-store? I think
if you want to have the offline deployer deploy to more config-stores
you can add configurations that start those config stores to the
offline-deployer-config.xml
I think the current behavior is fine.
thanks
david jencks