I also see no reason to use one as it doesn't deliver the most
important thing I would expect
from a container: "reloading the configuration without restarting
the server".
Is this the *most* important thing?
I think this is a personal interpretation of "most important thing"
of a container.
It's not just "personal interpretation". If users ask why was a
container needed for JAMES the standard answer is *flexibility*. Form
a user perspective flexibility means exactly that.
Maybe we're talking of different things: can you name a container
supporting out of the box configuration reloadability for its component
(with no full redeploy)?
No, we are not :). This is what a user understands under "flexibility" as a
"container"
has no meaning for most of the users.
Ahmed.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
