maybe you need to break the assosiaction 1st, since its not really a composition/parent-child relationship (compositions involve parent entity with multiplicity of 1 - in other words one parent/owner)
in a many-many relation between entity A and entity B, the join table we have unique fk pairs (a1, b1), (a1,b2), (a2,b1), (a2,b2) and so forth....these pairs form the PK for the join table. where a's are instances of A and b's are instances of B. Since its a bi directional relation, a1.addB(b1) and b1.addA(a1) happens. As they are sets. I think you might have to un-associate the ends before you delete otherwise it gives a constraint violation exception. so if you were to delete b1, try 1st b1.removeA(a1) a1.remove(b1) a2.remove(b1) and b1.removeA(a2) and then do delete(b1)....and maybe depending upon the mapping, you might justh ave to remove from one sise of the set and the join from join table gets removed thus successfully unassociating the relation.... Then I think it will work. -- View this message in context: http://www.nabble.com/many-to-many-relationship-%28bi-or-uni-directional%29-handling-delete-on-the-repository-tp18747005s17564p18749065.html Sent from the Fornax-Platform mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Fornax-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fornax-developer
