| Craig Russell (JIRA) 2007-02-06, 7:11 pm |
|
[ https://issues.apache.org/jira/brow...ls:all-tabpanel ]
Craig Russell reassigned JDO-442:
---------------------------------
Assignee: Craig Russell
> Transaction.setRollbackOnly() : difference between api20 and spec
> -----------------------------------------------------------------
>
> Key: JDO-442
> URL: https://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
> Assigned To: Craig Russell
> Fix For: JDO 2 maintenance release 1
>
>
> in the JDO2-final spec 13.4.5
> <spec>
> 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.
> </spec>
> 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
> <code>JDOUserException<code>."
> So which exception should be thrown here ... JDOFatalDataStoreException or
> JDOUserException ?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
|