> You may have noticed - tomcat doesn't work with JMX 1.2 > 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.
If you need new additions and fixes in JMX1.2, then switching to 1.2 sounds good to me. What other changes are needed to make it work with JMX1.2? I can volunteer to make the changes (especially in mbeans-descriptors.xml) if you point me to the list of changes. Amy > > Opinions ? Volunteers :-) ? > > Costin > > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
