Issue Details (XML | Word | Printable)

Key: JDO-415
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Minor Minor
Assignee: Craig Russell
Reporter: Marc Prud'hommeaux
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
JDO

DataStoreConnection assumes datastore transactions are being used

Created: 30/Aug/06 08:59 AM   Updated: 05/Oct/06 02:49 AM
Return to search
Component/s: tck2
Affects Version/s: JDO 2 final
Fix Version/s: JDO 2 maintenance release 1, JDO 2 TCK challenge fixes

Time Tracking:
Not Specified

File Attachments:
  Size
Text File Licensed for inclusion in ASF works JDO-415.patch 2006-10-03 10:53 PM Craig Russell 2 kB

Resolution Date: 05/Oct/06 02:45 AM


 Description  « Hide
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.



 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Marc Prud'hommeaux made changes - 06/Sep/06 08:25 AM
Field Original Value New Value
Link This issue is cloned as JDO-418 [ JDO-418 ]
Marc Prud'hommeaux made changes - 06/Sep/06 08:27 AM
Link This issue is cloned as JDO-418 [ JDO-418 ]
Craig Russell made changes - 02/Oct/06 08:08 PM
Assignee Craig Russell [ clr ]
Description
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.

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.

Craig Russell made changes - 03/Oct/06 10:53 PM
Attachment JDO-415.patch [ 12342224 ]
Craig Russell made changes - 04/Oct/06 09:28 PM
Fix Version/s JDO 2.0 TCK challenge fixes [ 12312093 ]
Fix Version/s JDO 2 maintenance release 1 [ 12310923 ]
Craig Russell made changes - 05/Oct/06 02:45 AM
Status Open [ 1 ] Resolved [ 5 ]
Resolution Fixed [ 1 ]