Uploaded image for project: 'JDO'
  1. JDO
  2. JDO-653

Extra checks in PMF.close tests

    Details

    • Type: Test
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: JDO 2 maintenance release 2 (2.2)
    • Fix Version/s: JDO 3 (3.0)
    • Component/s: tck
    • Labels:
      None

      Description

      Some of the implications of section 11.4 don't appear to be checked for in the case of an already-closed PersistenceManagerFactory.

      1. If close() is called on an already-closed PMF (with correct permission i.e. "closePersistenceManagerFactory"), no exception should be thrown.

      2. If close() is called on an already-closed PMF (without correct permission), exception should be thrown (even though it would otherwise do nothing).

      3. If close() fails (throws JDOUserException) due to active transaction(s), then none of the PersistenceManager objects belonging to the PMF should have actually been closed.

      4. Several get/set pairs are not tested for their behaviour after close()

        Attachments

        1. JDO-653.patch
          9 kB
          Peter Dettman
        2. JDO-653-2nd.patch
          11 kB
          Peter Dettman
        3. JDO-653-tck.patch
          11 kB
          Peter Dettman

          Activity

            People

            • Assignee:
              mcaisse Michelle Caisse
              Reporter:
              pkd Peter Dettman
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: