Hi Diego,
Are you using any MX4J implementation specific API?
Java SE 5.0 has its own implementation of JMX, so if you're only using public
JMX APIs defined in javax.management and subpackages, your code should
compile and run right away on Java SE 5.0. You won't even need the
MX4J packages in your classpath.
Give it a try.
If you're using MX4J implementation specific APIs (or MX4J specific protocols)
not covered by the JMX standard then you'll have to do a deeper analysis.
Best regards,
-- daniel
http://blogs.sun.com/jmxetc
Thank you very much Daniel!
My problem was that some mx4j class was implemented also by JAVA 1.5 core API (rt.jar). So at loading time JVM loaded rt.jar classes... not mx4j.jar classes. I solved the problem putting mx4j.jar in endorsed directory... in this way classes are searched in mx4j.jar first than in rt.jar.
Best regards
Diego
Yes I tried but the application, once started, was blocked on a infinite loop in the method scanTag... which performs parsification of mbeans.mlet file. Probably there are differences between mx4j implementation an rt.jar implementation regarding to this parsification function.
I'll investigate better.
Thank you very much again.
Diego