db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig Russell (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JDO-415) DataStoreConnection assumes datastore transactions are being used
Date Mon, 02 Oct 2006 20:10:20 GMT
     [ http://issues.apache.org/jira/browse/JDO-415?page=all ]

Craig Russell updated JDO-415:
------------------------------

    Description: 
org.apache.jdo.tck.api.persistencemanager.DataStoreConnection assumes that the connection
returned from getDataStoreConnection will be re-used once a JDO transaction is started, but
that assertion is only valid when using datastore transactions, and the test case does not
ensure that a datastore transaction is being used.

The solution is to call "getPM().currentTransaction().setOptimistic(false);" just before "getPM().currentTransaction().begin();"
in the testDataStoreConnection() test case.



  was:

org.apache.jdo.tck.api.persistencemanager.DataStoreConnection assumes that the transaction
returned from getDataStoreConnection will be re-used once a JDO transaction is started, but
that assertion is only valid when using datastore transactions, and the test case does not
ensure that a datastore transaction is being used.

The solution is to call "getPM().currentTransaction().setOptimistic(false);" just before "getPM().currentTransaction().begin();"
in the testDataStoreConnection() test case.



       Assignee: Craig Russell

> DataStoreConnection assumes datastore transactions are being used
> -----------------------------------------------------------------
>
>                 Key: JDO-415
>                 URL: http://issues.apache.org/jira/browse/JDO-415
>             Project: JDO
>          Issue Type: Bug
>          Components: tck20
>    Affects Versions: JDO 2 final
>            Reporter: Marc Prud'hommeaux
>         Assigned To: Craig Russell
>            Priority: Minor
>
> org.apache.jdo.tck.api.persistencemanager.DataStoreConnection assumes that the connection
returned from getDataStoreConnection will be re-used once a JDO transaction is started, but
that assertion is only valid when using datastore transactions, and the test case does not
ensure that a datastore transaction is being used.
> The solution is to call "getPM().currentTransaction().setOptimistic(false);" just before
"getPM().currentTransaction().begin();" in the testDataStoreConnection() test case.

-- 
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

        

Mime
View raw message