I've been working around the area effected by this
issue, but thought I'd try to get some more info/spawn
some more thought on this topic. There's a comment in
the ClassMolder.getIdentity(TransactionContext,
Object) method code that says: "In the case where key
generator is used, the value of identity is dummy, set
it to null". Wouldn't this statement be limited to
objects being newly created? The problem that I see
is that it doesn't allow for accessing the identity of
an existing object in a long transaction (i.e. where
the existing object hasn't been marked persistent.
The workaround I'm considering is to load the castor
mapped objects prior to calling Database.create on the
object that has these objects as field members in
order to have the create method correctly get their
identities. This seeems like a terribly inefficient
solution (I'm introducing 3 unnecessary db queries)
for one save operation. Are there other alternatives?
Thanks,
Jon
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
