Hi all
Some news on my problem ... In fact this behavior ( deletion of
roles
when removing the cross reference ) only occurs when I'm NOT using the
ObjectCacheDefaultImpl caching strategie.
It's strange to me ?
Le sam 28/02/2004 à 02:32, olivier.nouguier a écrit :
Hi all,
I'm
Hi all,
In fact I think I found that when cache is NOT the default, the
collection used are the RemovalAwareCollection then the BUG is on the
afterStore callback.
Am I right? Is there another solution?Why did such collection are used
in this case?
Thank
Have a nice end week
For M:N mappings, you should not use auto-delete (that will remove the M or N side -
depending on config/code). You should use 'auto-delete=false' and a
'collection-class=org.apache.ojb.broker.util.RemovalAwareCollection' (I don't remember
the
complete class name - please, double check it).
This
Hi
And thanks for this PB tips!
But it doesn't seems to work with odmg, in fact I saw ( comment in
source ) that RemovalAwareCollection are there to be used with PB
This will allow to use the PB api in way pretty close to ODMG persistent
collections! ( dixit Thomas Mahler ).
Hi all,
I'm really lost with auto-delete feature...
The model:
0,n 0,n
Actors Roles
The RDBMS schema:
actors ( id, ... )
roles ( id, ... )
actors_roles ( actor_id, role_id )
The problem:
With the attached repository.xml, when I remove
