You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ojb-user@db.apache.org by Armin Waibel <ar...@code-au-lait.de> on 2004/01/13 13:26:49 UTC

Re: java.lang.ClassNotFoundException: org.apache.ojb.broker.util.collections.RemovalAwareCollection

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.ojb.broker.util.collections.ManageableArrayList
or your own implementation of ManageableCollection. But you will these 
classes on client side too.

 > Is ojb always returning a java.util.Collection?
per default - yep. More info see
http://db.apache.org/ojb/repository.html#collection-descriptor

regards,
Armin

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



---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-user-help@db.apache.org