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
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
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
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
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
