It interests me too, but I did not have time for this. However, since this is just another protocol implementation, you should use it with standard tools (like jconsole). Just make sure it is in the classpath and provide a valid service URL, possibly something like "service: jmx: ws: // localhost: 8080 / test" when connecting.
If you look here http://java.sun.com/javase/6/docs/technotes/guides/management/jconsole.html , then there is an example of how to extend the class path when running jconsole. I used this technique for several other protocols and it usually works.
, JSR-262-ri.jar, jar lib , , , :
SEVERE: The JAX-WS 2.1 RI is not Sun unbundled RI.
JAX-WS jars must be located in your classpath when running on JDK 5 and JDK 6 update release 4 (or higher).
If running on a previous JDK 6 (JDK 6 to JDK 6 update 3 included) you need to use the endorsed directory .
NB: The JAX-WS 2.1 release bundled in JDK 6 cannot be used to run this Connector. The unbundled release of JAX-WS 2.1 is required.
This wrong release is loaded from : the bootclasspath.
, - , , ... , . , , .
, , , , .
: Java , MBeans, delphi ( - )? , : -)