Costin Manolache wrote:
You may have noticed - tomcat doesn't work with JMX 1.2That seems ok to me, but we should switch back to MX4J ASAP after that. (but I don't have time to help these days, unfortunately)
The main problem is that the spec now requires the type to be JNI-style ( [Ljava.lang.String; instead of java.lang.String[] ).
That would require a change in mbeans-descriptos.xml - but I'm
not sure if mx4j would still work after that.
There are also some additions and fixes in JMX1.2 we may need
( like sending the attribute change notifications to all listeners -
that works in jboss-jmx, but not in mx4j and jmx1.1-ri ).
Should we switch to ri-1.2 until MX4J finishes the update to 1.2 ?
The license seems more relaxed now - so we may be able to redistribute
it without problems. Obviously MX4J should be preffered for the release.
Opinions ? Volunteers :-) ?
Remy
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>