If different protocols are desired beyond that and we support them, you can just add the dependent JARs and they become available.
I think this is what you want ...
I think this is a bad idea. If I want a specific connector available on my server, I will explicitly deploy it. I may want SOAP for something other then JMX remoting and I don't want it to implicitly available as a JMX connector just because I have some jars in my classpath.
-dain
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
