I've fixed this in CVS. Please test the fix. TIA
St-Pierre Philip wrote:
I have a many-to-many association between two objects. The association
table contains the idbag identifier, the identifier of each associated
objects and additionnal fields (Collection of components). Here is the
associat
OK, I took a look at this.
I am happy with this behavior, it gives consistent semantics for lock(),
and exhibits the reasonable
behavior that a vetoed update() results in a lock().
In general, Lifecycle is no longer something we really recommend and we
are creating a whole new
event API in Hibe
Thanks for the detailed description!
First of all I might have been easy to misunderstand, but I don't want
to try to implement auditing in general. My knowledge is not enough for
that right now.
I have a project that implements auditing so, that I have a
SITE_QUESTION_ASSOCIATION table/entity t
