[jetty-discuss] Re: Jetty JMX support

[Christian K. <cke...@in...>]

Ok, I'll have a look at this over the weekend. Any experience with MX4J 
v3.x vs. Jetty?

Chris


On Mar 25, 2005, at 4:34 PM, Jan Bartel wrote:

> Christian,
>
> I suppose we need to update the version of MX4J that ships with Jetty, 
> I guess it is rather old now.
>
> Note that if you want to upgrade to a newer MX4J, you don't have to 
> modify org.mortbay.util.jmx.Main, you can write your own Main class 
> and run it instead:
>
> java -Dstart.class=<your Main> -jar start.jar <your mlet>
>
> If, however, you wanted to update org.mortbay.util.jmx.Main for a 
> newer MX4J, I'm sure your contribution would be gratefully received 
> and included in the next release. :-)
>
> regards
> Jan
>
>
> Christian Kesselheim wrote:
>> Hi everybody!
>> I just hacked the eclipse jettylauncher plugin so I could run jetty 
>> plus in jmx mode from my favourite IDE, while trying to access my 
>> beans via MC4J and its RMI connector support.
>> Unfortunately, jetty plus seems to still rely on the old and 
>> deprecated API of MX4J prior to JSR160. Even worse, it doesn't event 
>> ship any version of mx4j that would include the necessary adaptor 
>> classes in question, as they're no longer included in their (MX4J) 
>> binary distribution:
>> ==== (snip) =====
>> MX4J's Deprecated Tools
>> ~~~~~~~~~~~~~~~~~~~~~~~
>> + The JRMPAdaptor and the IIOPAdaptor were tools that allowed 
>> connection with a
>>   remote MBeanServer via plain RMI and via CORBA's IIOP protocol.
>>   Since MX4J 2.x now implements the standard JMX Remote API (JSR 
>> 160), these
>>   tools are not mantained anymore and they're not shipped with the 
>> binary
>>   distribution, to protote use of the standard JMX Remote API.
>>   They're still present in the source distribution and can be 
>> compiled using the
>>   provided build file if needed.
>>   Their usage is strongly discouraged, though, and they will not be 
>> supported
>>   any longer.
>> ==== (snap) =====
>> Hence, in order to allow some configuration like this:
>> <MLET
>>   NAME="mx4j.adaptor.rmi.jrmp:type=jrmp"
>>   CODE="mx4j.adaptor.rmi.jrmp.JRMPAdaptor"
>>   ARCHIVE="mx4j-tools.jar">
>> </MLET>
>> one would need to build MX4J from source and add the those jars to 
>> jetty. Are there other ways of dealing with this except hacking 
>> jetty-5.1.3rc3/src/org/mortbay/util/jmx/Main.java?
>> Best regards,
>> Christian Kesselheim
>> -------------------------
>> infeurope S.A.
>> 62, rue Charles Martel
>> L-2134 Luxembourg
>> Luxembourg
>> Tel: (+352) 25.22.33.1
>> Fax: (+352) 25.22.33.222
>> Web: www.infeurope.lu
>> -------------------------
>> Any views expressed are purely those of the writer and may not in any
>> circumstances be regarded as stating an official position of 
>> infeurope S.A.!
>> -------------------------------------------------------
>> SF email is sponsored by - The IT Product Guide
>> Read honest & candid reviews on hundreds of IT Products from real 
>> users.
>> Discover which products truly live up to the hype. Start reading now.
>> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>
>

-------------------------
infeurope S.A.
62, rue Charles Martel
L-2134 Luxembourg
Luxembourg
Tel: (+352) 25.22.33.1
Fax: (+352) 25.22.33.222

Web: www.infeurope.lu
-------------------------

Any views expressed are purely those of the writer and may not in any
circumstances be regarded as stating an official position of infeurope 
S.A.!