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 client, it contains a reference to the implementation class (RemovalAwareCollection), which must be available to the client either on the local classpath or via the URL class loader.
You can control the class used for collection handling in the OJB.properties file. Thus, you could write your own class to handle the collection if you want to avoid distributing the OJB jar file.
I hope that helps, and if I've horribly misstated something, I'm sure someone will correct me :-)
Christopher Tava wrote:
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 always returning a java.util.Collection? I see a ManageableCollection class in the broker package? Does that have anything to do with it?
Thank you in advance for you much needed reply.
Sincerely, Chris
---------------------------------
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
-- Larry V. Streepy, Jr. Senior Vice President and CTO Health Language, Inc.
