Hi Yes it is normal. When you have a main object that has a collection attribute, Ojb works just on value objects that are in the collection.
I developed a framework based on Ojb called mandragora ( http://mandragora.sourceforge.net) that provides lots of method that can help. The methods updateCollectionReference, updateCollectionReferences and updateCreateTrees do just what you need http://mandragora.sourceforge.net/referenceguide/bd-api-guide.html Have a look. Documentation is very poor but in the following days I will upload something more I hope this can help Best Regards Alessandro On 9/12/07, Alessandro Colantoni <[EMAIL PROTECTED]> wrote: > > > > On 9/12/07, Hans Novak <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > i am not shure, but is ist correct when i have an object, witch is a > > tree of some other objects (colletions) and i delete a part of the tree > > and then store the hole object (tree) - in the database the deleted > > object will also be deleted ? > > > > Everything works fine, when i store or update the object, but not when i > > delete. > > The deleted part of the object will not be deleted in the database. I > > can remove it by hand, when i run a remove.object (the part of the > > tree) and then store the (changed) tree. > > > > Is this normal ? > > > > > > Hans > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > >
