Uploaded image for project: 'Jackrabbit Content Repository'
  1. Jackrabbit Content Repository
  2. JCR-3195

wrong assumptions in test cases about lock tokens

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.3.6
    • Fix Version/s: 2.3.7
    • Component/s: jackrabbit-jcr-tests, test
    • Labels:
      None

      Description

      Several test cases assume that Lock.getLockToken has to return null for locks not attached to the current session. However, this is optional. Citing the Javadoc for getLockToken:

      • May return the lock token for this lock. If this lock is open-scoped and
      • the current session either holds the lock token for this lock, or the
      • repository chooses to expose the lock token to the current session, then
      • this method will return that lock token. Otherwise this method will
      • return <code>null</code>.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                reschke Julian Reschke
                Reporter:
                reschke Julian Reschke
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: