RE: Re: Implementing new JSR 160 providers: volunteers ?

Hi Gustavo, 

> It's funny that I'm working on another open source project, 
> MyGrid (see
> www.ourgrid.org) trying to put a instrumentation/management 
> layer based on
> JMX. They are using RMI for remote communication, and I was 
> thinking it
> would be great if I could use Hessian/Burlap for that, 
> without loosing the
> JSR 160 benefits (notification, monitoring).
> 
> So I guess that I'm raising my hands now. I'll take a look at 
> the source code for the other implementations.

The Hessian/Burlap stuff is done and committed in CVS, but I discussed with Scott Ferguson (Hessian guru) what would have been the best way to implement the Hessian serialization.
Right now I have taken the simplest way: use Java serialization. Unfortunately, this will work only with Java clients, and rules out any other non-Java client.
The alternate solution is to write Hessian's custom serializer/deserializer for most serializable JMX classes, which is a boring task, but the best solution.

Give a try to the Hessian stuff, and let us know. It requires Jetty for HTTP transport, and works pretty much like the SOAP connector of which you can find information here:
http://mx4j.sourceforge.net/docs/ch03s20.html

JMXServiceURL are of course

service:jmx:hessian://host:8080/whatever
service:jmx:burlap://host:8080/whatever

Simon


-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285