Re: MX4J and J2SE 5.0

Hi,

> What's the plan for making MX4J work under J2SE 5.0?
>
> As far as I can tell, Sun doesn't want users to override the JMX
> implementation that ships with 5.0:
>
>   http://java.sun.com/j2se/1.5.0/docs/guide/standards/
>
> Suppose I want to use MX4J anyway.  In theory, I should be able to do
> this by putting MX4J on the bootclasspath.  In practice, this means
> that all of MX4J's dependencies -- including commons-logging and such
> -- have to go on the bootclasspath as well.  Putting commons-logging
> on the boot or system classpath is not a great idea in many
> situations.  Is there any interest in replacing the dependency on
> commons-logging with java.util.logging.*?

MX4J should work standalone, without requiring additional jars.
They're required for compilation, but not at runtime.

If it's only for the logging, to make MX4J use java.util.logging
facilities, then you should extend mx4j.log.Logger and delegate to a
JDK 1.4 logger, very much like it's done for the Log4JLogger.

In general, I've tried using MX4J from the boot classpath (JMX and JSR
160 implementations only) and it worked fine.

The other option is to leave MX4J in the classpath and use
-Djavax.management.builder.initial=mx4j.server.MX4JMBeanServerBuilder,
which will replace the MBeanServer implementation: you get ObjectName
(and other concrete classes) implementation from Sun, but MBeanServer
implementation from MX4J.

The JSR 160 implementation is completely pluggable, so you can use
MX4J's implementation of rmi and iiop instead of JDK's ones.

Do you have specific problems ?

Simon
--
http://bordet.blogspot.com


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php