Re: setRollbackOnly() and what is thrown by commit()

[Craig L Russell]

Hi Andy,






Thanks,

Craig

On Nov 13, 2006, at 4:52 AM, Andy Jefferson wrote:

Good catch. It's definitely a spec bug that I expect that we should fix in a maintenance release. Please file a JIRA. We should probably have a test case written for it as well.

Hi,

in the JDO2-final spec 13.4.5
<spec>

when the transaction has been marked for rollback.
</spec>


committed, and any attempt to commit the transaction will throw
<code>JDOUserException<code>."


JDOUserException ? probably the version in the spec.

Do you require a JIRA ?

--
Andy

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 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 So which exception should be thrown here ... JDOFatalDataStoreException or

Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:[EMAIL PROTECTED]
P.S. A good JDO? O, Gasp!

smime.p7s
Description: S/MIME cryptographic signature