Could do, although the issue there is that MX4J doesnt implement the JMXMP connector and instead have its own connectors based on soap, hessian, or burlap which all require Jetty or such like to communicate via http, so that means adding that too on broker and console sides.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Aidan Skinner Sent: 01 December 2008 10:19 To: [email protected] Subject: Re: [jira] Commented: (QPID-1469) AMQUserManagementMBean.getCurrentJMXUser no longer returns a valid user[MESSAGE NOT SCANNED] On Mon, Dec 1, 2008 at 1:24 AM, Robbie Gemmell <[EMAIL PROTECTED]> wrote: > One issue with making it on by default is that everyone will need to download the jmxremote_optional.jar and add it to the classpath to start the broker, even for testing...which I believe is the reason it was turned off by default in the first place, I recall seeing it in a commit message when scouring the backlog previously. We should probably integrate MX4J (http://mx4j.sourceforge.net/) instead, this is what Tomcat, Geronimo etc use. The OpenDMK stuff seems to still be propreitary, although it's a little hard to tell if that's intentional or not. - Aidan -- Apache Qpid - World Domination through Advanced Message Queueing http://cwiki.apache.org/qpid "Have we anything resembling a plan?" "Mm-hm. Ride till we find them... and kill them all." - The 13th Warrior
