I've got a question regarding the default behavior of OJB. Given a M:N relation which is being decomposed with a standard indirection table, the default collection class (RemovalAwareCollection) is deleting the target objects when they are removed from the subject. This seems counter-intuitive to the typical use cases where M:N relations exist to relate objects that have their own life cycle.

Wouldn't it be more intuitive for OJB to use a normal ManageableVector unless the collection descriptor indicated that auto-delete="true"?

My basic point is that it would seem more "correct" if the auto-delete setting controlled the default collection class to be used for a collection instance.

Comments? Am I missing some other obvious rationale?

Thanks.

--
Larry V. Streepy, Jr.
Senior Vice President and CTO
Health Language, Inc.

Reply via email to