db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Jefferson (JIRA)" <j...@apache.org>
Subject [jira] Created: (JDO-442) Transaction.setRollbackOnly() : difference between api20 and spec
Date Mon, 13 Nov 2006 20:37:37 GMT
Transaction.setRollbackOnly() : difference between api20 and spec

                 Key: JDO-442
                 URL: http://issues.apache.org/jira/browse/JDO-442
             Project: JDO
          Issue Type: Bug
          Components: api2, api2-legacy, specification
    Affects Versions: JDO 2 final
            Reporter: Andy Jefferson
             Fix For: JDO 2 maintenance release 1

in the JDO2-final spec 13.4.5
Once a transaction has been marked for rollback via setRollbackOnly, the 
commit method will always fail with JDOFatalDataStoreException. The JDO 
implementation must not try to make any changes to the database during commit 
when the transaction has been marked for rollback.

whereas in the javadocs for javax.jdo.Transaction "setRollbackOnly" we have
"Sets the rollback-only status of the transaction to <code>true</code>. After

this flag is set to <code>true</code>, the transaction can no longer be 
committed, and any attempt to commit the transaction will throw 

So which exception should be thrown here ... JDOFatalDataStoreException or 
JDOUserException ?

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message