Really, executing again withou my patch, I've seen that is not the keys, but the field
it
self. Sorry...
The line getting in trouble is
Object col = cds.getPersistentField().get(obj);
because there is no persistent field at all.
I'm a bit lost in too much code, techs, newbie programmers, and so on here...
I think
1) if we use getCascadeDelete != true early, we can have trouble with M:N
relationships;
2) if we use later, we get a non existent property exception because the field just
don't
exist in the bean.
As far as I can see, this is the way the virtual attribute affect the OJB behavior.
Thanks,
Edson Richter
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
