This is a known problem with
This class allows serialised objects to be passed over
the network and if the client doesn't have the class
for the object, rmi will retrieve the class from the
However, the data passed to allow rmi to perform this
operation can get very large.
We are looking at different mechanisms that will avoid
using MarshalledObjects but this is still a Work in
Witch classes, Application or JBoss classes ?
One possible solution to this problem is to sub-class
Object(Input/Output)Stream to include a ClassLoader
that can talk back to the server when the class is
not available locally.
This avoids having use MarshalledObjects, and only
classes not available in the client are download
from the server.
Currently all objects have to be "marshalled" just
in case the client doesn't know about the its class.