You're right, the exception is now different ! :)
It looks like db.update tries to create a new instance instead of just
updating (org.exolab.castor.jdo.DuplicateIdentityException). Not sure
why this is happening, I guess there's something wrong with my setup,
otherwise everybody would have complained about it by now...
Bruce Snyder wrote:
>This one time, at band camp, Cezar@Home said:
>
>C>I'm trying to use long transactions to update persistent objects loaded
>C>in previous transactions. I'm also using oracle sequences to generate
>C>primary keys.
>C>When trying to commit the "UPDATED" changes, the sequence gets somehow
>C>involved and I don't understand why...
>C>i'm getting the following exception:
>C>
>C>org.exolab.castor.jdo.PersistenceException: The identity of a data
>C>object of type com.perfuse.domain.Company, has been changed from 109,373
>C>to 109,376 since it is loaded/create/update.
>C> at org.exolab.castor.persist.ClassMolder.preStore(ClassMolder.java:1126)
>C> at org.exolab.castor.persist.LockEngine.preStore(LockEngine.java:723)
>C> at
>C>org.exolab.castor.persist.TransactionContext.prepare(TransactionContext.java:1379)
>C> at
>C>org.exolab.castor.jdo.engine.DatabaseImpl.commit(DatabaseImpl.java:499)
>C> at Runner.main(Runner.java:89)
>
>Cezar,
>
>If you remove the key generator and just handle the object id
>manually, do you get the same thing? BTW, I'm guessing you won't.
>
>Bruce
>--
>
>perl -e 'print unpack("u30","<0G)U8V4\@4VYY9&5R\"F9E<G)E=\$\!F<FEI+F-O;0\`\`");'
>
>-----------------------------------------------------------
>If you wish to unsubscribe from this mailing, send mail to
>[EMAIL PROTECTED] with a subject of:
> unsubscribe castor-dev
>
>
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
