Hi, Wallace explanation is correct. But OJB also provides support for user defined collection classes! To let OJB handle such a user-defined Collection it must implement the callback interface ManageableCollection. This interface provides hooks that are called by OJB during object materialization, updating and deletion.
(BTW this is mentioned in tutorial3.html only two lines beneath the sentence you quote !) cheers, Thomas Gelhar, Wallace J. wrote: > It is...But you have to reference only the Collection interface which > means you must declare > > Collection foo = new FooCollection(); //since FooCollection implements > Collection this works > > And not > > FooCollection foo = new FooCollection(); //OJB looks at the type of the > member FooCollection > > OJB Knows nothing about a FooCollection. > > -----Original Message----- > From: David Corbin [mailto:[EMAIL PROTECTED]] > Sent: Friday, September 06, 2002 10:12 AM > To: OJB Users List > Subject: Populating Colletions > > > I know that the documentation says, types |java.util.Collection, > java.util.List, java.util.Vector are the only ones supported when > mapping 1:n relationships. I can testify to the truth of this, but my > question is WHY? > > If I have a member "Collection foos", my code works fine. If I have > "FooCollection foos", and FooCollection implements Collection, it > doesn't work. But I don't see any logical reason for this limitation, > since the method of storing and retreiving data is the same. As far as > OJB is concerned, it should be treated as a Collection. So, why is isn't > it? > > Thanks > David > | > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
