On Nov 13, 2007, at 9:36 PM, Gianny Damour wrote:
Hi Joe,
After some investigations, here is my understanding of problem 1:
there are two deployments because by default, i.e. when no target is
specified, the distribute command executes against all the
configuration stores defined by a Geronimo instance. Note that this
default behavior is also applied by other deployment components,
such as the hot directory scanner or the installation portlet. To
some extent, I believe this default behavior should be changed to
deploy to only one configuration store. Indeed, I am not convinced
that users distributing applications would expect their applications
to be deployed as many times as the number of configuration stores
defined by the targeted Geronimo server. Also, having the same
configuration multiple times in a Geronimo instance does not make a
lot of sense.
A potentially better default behavior would be: only distribute to
the first target returned by DeploymentManager.getTargets().
Internally, our implementation of getTargets returns as the first
target the "default" configuration store.
Problem 3) is caused by problem 1).
What do you think?
Hi Gianny,
That seems like reasonable behavior.
I haven't looked closely at this, yet. I'm curious about how list-
modules would work. I'm also wondering about plugin installation,
console support, etc. Have they been updated appropriately to reflect
your multiple config store scheme?
--kevan
