"Bruce Snyder" <[EMAIL PROTECTED]> wrote:
> This one time, at band camp, Steffen Fiedler said:
[...]
> SF>How can i avoid the Exception:
> SF>"org.exolab.castor.jdo.DuplicateIdentityException: update object
> SF>which is already in the transaction"
> SF>while using long transactions? The affected objects don't have
> SF>to be changed in this situation and read-only="true" doesn't
> SF>change anything.
> SF>The only way i found is to change objects by loading them and
> SF>all there linked objects in short transactions.
> SF>But i think, its not the best way...
>
> Have you tried to use jdo.setAutoStore( true )? I'm curious to know how
> that affects your situation.
The error occurs with setAutoStore(true).
When i setAutoStore(false) i get the org.exolab.castor.jdo.PersistenceException,
that the linked objects of my updated object are not loaded/updated/created
in this transaction. Only loading them apartly is working.
Steffen
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
