I use exactly same config and works as expected, except I use proxies.
There is any chance you be issueing a delete(Object o2), that is deleting the "n"
related object?
I'm using either rc4 and rc5 (latest from CVS). What version are you using? Are you
using proxies?
Edson Richter
----- Original Message -----
From: Klaus Ripplinger
To: [EMAIL PROTECTED]
Sent: Wednesday, March 03, 2004 2:18 PM
Subject: delete relation in indirection-table
Hi,
my problem: how to delete a relation when using "Non-Decomposed m:n Mapping".
After removing an object from a collection (RemovalAwareCollection) and
saving the object
(PersistenceBrokerFactory.defaultPersistenceBroker().store(Object o)) not only
the relation is deleted but also the ralated object, i.e. the one
that has been removed from the collection. Can this be avoided? F.e. i don't
want to delete a 'project' when removing a 'project' from 'user'. Only the entry
in the
indirection-table that mapps projects to users should be deleted.
Regards
Klaus
collection xml:
...
<collection-descriptor
name="projects"
collection-class=
"org.apache.ojb.broker.util.collections.RemovalAwareCollection"
element-class-ref="com.imd.paris.base.Projects"
indirection-table="user_projects"
auto-delete="false"
auto-update="true">
<fk-pointing-to-this-class column="user_id"/>
<fk-pointing-to-element-class column="project_id"/>
</collection-descriptor>
...
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.605 / Virus Database: 385 - Release Date: 1/3/2004
