I'll try to answer your question, although I'm still somewhat new to OJB
myself.
OJB uses RemovalAwareCollection as the default implementation class for
holding the collection instance. RemovalAwareCollection implements
java.util.Collection. So, when your container class is serialized to
the
Hi Christopher,
per default OJB use a
org.apache.ojb.broker.util.collections.RemovalAwareCollection for
populating 1:n relations. Thus you need this class on client side too.
You can change this default class by setting a
'collection-class' attribute in collection-descriptor.
e.g. org.apache.oj
Dear OJB User Group,
I am using OJB in jboss and making an EJB connection to the server and it
seems like the client application is trying to down a server side class.
Any suggestion as to what can be the problem that cause the rmi classloader to
reference the RemovalAwareCollection.
Is ojb
