Costin Manolache wrote:
We could - but since JMX is in JDK anyway, I don't think it's that
important
to
wrap it or not have a code dependency. Wrapping won't make it lighter at
runtime :-)
I thought you wanted to provide a modeler implementation using a more
lightweight component model for your mini Tomcat.
I should just clean up the few places where jmx is abused ( i.e. used as an
introspection
equivalent in normal code paths ). It's use should be limitted to
'management' - i.e. configure and get runtime info.
I liked your earlier idea of removing all direct dependencies.
Rémy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
