Costin Manolache wrote:
It's not about using a mini-jboss architecture, but about a more
consistent and simpler
configuration.
IMO JMX should be used for configuration when possible, instead of
adding more weird
syntax to server.xml.
I tried it quite hard at some point (it's the embedded distribution),
and it didn't work out that well. It's actually more complex.
The first task is to optimize modeler (you'll do it, right ?), and then
maybe to use modeler exclusively in Tomcat (avoiding all direct JMX
dependencies).
What is 'core module' and not is a complex issue - obviously what
ships in the 'default' distro will
change with each release. But clustering seems like a big enough and
separate enough component to me, if this is not a good candidate for
'separate module' - I don't know what would be. It's clearly not used
by all users, it has 2 implementations, etc.
And it needs to get back to 1 implementation in a hurry :) I am
conceptually ok with it being a module, though, although I would be
happier if it was in the main tree (this way it's harder to ignore when
the build is broken).
Other opionions ?
Rémy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
