| Michelle Caisse (JIRA) 2006-03-27, 7:47 am |
| Assertion Description does not match ASSERTION_FAILED String in lifecycle.NontransactionalWriteThrows.java
-----------------------------------------------------------------------------------------------------------
Key: JDO-350
URL: http://issues.apache.org/jira/browse/JDO-350
Project: JDO
Type: Bug
Components: tck20
Reporter: Michelle Caisse
Priority: Trivial
*<B>Assertion Description: </B>
A5.6.2-4 [If a datastore transaction is begun, commit will write
the changes to the datastore with no checking as to
the current state of the instances in the datastore.
That is, the changes made outside the transaction
together with any changes made inside the transaction
will overwrite the current state of the datastore.]
A5.6.2-6 [If a datastore transaction is begun, rollback will not write
any changes to the datastore.]
A5.6.2-8 [If an optimistic transaction is begun, commit will write
the changes to the datastore after checking as to the current state
of the instances in the datastore. The changes made outside
the transaction together with any changes made inside the transaction
will update the current state of the datastore if the version
checking is successful.]
A5.6.2-10 [If an optimistic transaction is begun, rollback will not write
any changes to the datastore. The persistent-nontransactional-dirty
instances will transition according to the RestoreValues flag. ]
*/
public class NontransactionalWriteThrows extends NontransactionalWriteTest {
/** */
protected static final String ASSERTION_FAILED =
"Assertion A5.6.2 (NontransactionalWriteThrows) failed: ";
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secur...nistrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|