On Mon, Dec 1, 2008 at 10:46 AM, Robbie Gemmell <[EMAIL PROTECTED]> wrote:

> 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.

I think that's a better solution than saying "oh, hey, go download
this other random thing if you want authentication". That's just weak.

- 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

Reply via email to