Thanks Aaron and David,
I've modified o.a.g.client.builder.AppClientModuleBuilder and
o.a.g.deployment.Deployer to accept multiple ConfigurationStore
references, so now Geronimo will run with two ConfigurationStores
specified in system-plan.xml. As you guys expected, you can pass a
Target to the
You could start by just trying 2 config stores. Add another one to the
j2ee-system plan and rebuild everything. If the server starts we can
start worrying about how to put stuff there:-)
I'm very interested in using the geronimo repo as the immutable config
store: for at least gbean-only con
On Mon, Nov 21, 2005 at 02:24:48PM -0500, Aaron Mulder wrote:
> You could in theory have multiple config-stores, for example one
> read-only containing some core modules that are never supposed to
> change and one read-write for new deployments. However we haven't
> tested that adequately and I'm
ested that adequately and I'm not convinced it would really work
properly right now. I believe we do intend to make this work
eventually, I just don't think it's on the very short-term horizon.
Aaron
On 11/21/05, Nell Gawor <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I am trying to
Hi,
I am trying to figure out why the list-targets command for the deployer is
useful. It looks like it is only useful if you have multiple targets, and
therefore multiple config-stores. Without clusters, can you have multiple
config-stores? What would be the motivation?
Thanks,
Nell
