Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jdo-dev@db.apache.org
Message-ID: <28995248.1160016380088.JavaMail.root@brutus>
Date: Wed, 4 Oct 2006 19:46:20 -0700 (PDT)
From: "Craig Russell (JIRA)" <jira@apache.org>
To: jdo-dev@db.apache.org
Subject: [jira] Resolved: (JDO-415) DataStoreConnection assumes datastore
 transactions are being used
In-Reply-To: <33415898.1156928422277.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/JDO-415?page=all ]

Craig Russell resolved JDO-415.
-------------------------------

    Resolution: Fixed

svn commit src/java/org/apache/jdo/tck/api/persistencemanager
Sending        src/java/org/apache/jdo/tck/api/persistencemanager/DataStoreConnection.java
Transmitting file data .
Committed revision 453089.


> 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
>             Fix For: JDO 2 maintenance release 1, JDO 2.0 TCK challenge fixes
>
>         Attachments: JDO-415.patch
>
>
> 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