Details

    1. JDO-401.patch
      0.6 kB
      Craig L Russell

      Activity

      Hide
      Michael Bouschen added a comment -

      I merged the change from the trunk into brach 2.0.1 (see revision 452620).

      Show
      Michael Bouschen added a comment - I merged the change from the trunk into brach 2.0.1 (see revision 452620).
      Hide
      Craig L Russell added a comment -

      svn commit -m "JDO-401 Set Optimisitic to false to make sure jdoPreClear is called" src/java/org/apache/jdo/tck/api/instancecallbacks/CallingJdoPreclear.java
      Sending src/java/org/apache/jdo/tck/api/instancecallbacks/CallingJdoPreclear.java
      Transmitting file data .
      Committed revision 429837.

      Show
      Craig L Russell added a comment - svn commit -m " JDO-401 Set Optimisitic to false to make sure jdoPreClear is called" src/java/org/apache/jdo/tck/api/instancecallbacks/CallingJdoPreclear.java Sending src/java/org/apache/jdo/tck/api/instancecallbacks/CallingJdoPreclear.java Transmitting file data . Committed revision 429837.
      Hide
      Michael Bouschen added a comment -

      The patch looks good!

      Show
      Michael Bouschen added a comment - The patch looks good!
      Hide
      Craig L Russell added a comment -

      Right. The test was written assuming that the default transaction type was datastore. The test needs to be explicit by setting the transaction type to datastore regardless of the default.

      Show
      Craig L Russell added a comment - Right. The test was written assuming that the default transaction type was datastore. The test needs to be explicit by setting the transaction type to datastore regardless of the default.
      Hide
      Craig L Russell added a comment -

      Need to resolve these issues for maintenance release 1.

      Show
      Craig L Russell added a comment - Need to resolve these issues for maintenance release 1.
      Hide
      Ilan Kirsh added a comment -

      In org.apache.jdo.tck.api.instancecallbacks.CallingJdoPreclear:

      When optimistic transaction is used, In the commit in line 127 secondaryObj is expected to be persistent non transactional so it is not expected to be cleared, and jdoPreClear should not be called.

      Show
      Ilan Kirsh added a comment - In org.apache.jdo.tck.api.instancecallbacks.CallingJdoPreclear: When optimistic transaction is used, In the commit in line 127 secondaryObj is expected to be persistent non transactional so it is not expected to be cleared, and jdoPreClear should not be called.

        People

        • Assignee:
          Craig L Russell
          Reporter:
          Ilan Kirsh
        • Votes:
          0 Vote for this issue
          Watchers:
          0 Start watching this issue

          Dates

          • Created:
            Updated:
            Resolved:

            Development