RE: JSR 160 is FINAL !

Hi,

> That's great news - sounds like we can stick JSR 160
> into this release.  

That's the plan, yes

> I have started by digging into
> j.m.remote.compliance.serialization.RemoteJMXSerializationTest
> - and it looks like the
> j.m.r.c.s.support.RemoteInstantiator class is
> unimplemented (all methods return null).  

Yes. A skeleton I made some time ago.

> I've replaced these with instantiations - but the
> serialization verifier tries to serialize an object
> with one version of a class and deserialize it with
> another.  This will fail every time.  

That's strange.
The serialization stuff works fine with all JSR 3 classes, it is only a matter of having the Comparator implemented correctly, unless I am totally off road here.

> I'm working on
> an alternative approach to testing the serialization -
> but if anyone has any suggestions as to how to
> serialize an object with an MX4J javax.management. ..
> classloader and deserialize it with a Sun RI
> classloader - let me know.

Before writing something new, take a look at how the tests for JSR 3 work.
They should be very very similar for JSR 160. Given that, it should be sufficient to implement the RemoteInstantiator and the RemoteComparator. The rest should do the job.
In fact, the serialization tests for the JSR 160 part inherit from the one of the JSR 3 part.

Let me know if you have further problems.

Simon


-------------------------------------------------------
This SF.net email is sponsored by: The SF.net Donation Program.
Do you like what SourceForge.net is doing for the Open
Source Community?  Make a contribution, and help us add new
features and functionality. Click here: http://sourceforge.net/donate/