use of custom ObjectStream with CL

[marc.fleury]

in JRMPInvoker (org.jboss.invocation.jrmp.server.JRMPInvoker) we use the java.rmi.MarshalledObject serialization deserialization, the net result is
1- Heap massacre we create byte[] stuff all over the face
2- the codebase annotation is killing us and adding crap in the serialization

talk to me to get pointers on how to get started on this it should be a couple of days work

[adrian.brock]

Hi Marc,

After giving myself a quick crash course in how
the proxies work, I cant figure out how to
plugin the custom objectstream.

The externalization seems to take place within
the UnicastRemoteObject code?

I think I need your pointers.

Regards,
Adrian

[adrian.brock]

I've just been looking at the 1.4 rmi docs.

There's an RMIClassLoaderSpi
that lets you override most of the interesting
classloader functions including
getClassAnnotation(Class)

Shame it's 1.4 :-(

Regards,
Adrian

[marc.fleury]

How are you doing there warjort you got it?

let me know privately (email) if you want the OSCL class and we can do that optimization. we can overwrite the class annotation by overwritting the getURL in the UnifiedClassLoader (ex URLClassLoader).

Try to get some numbers on both versions.