Details

    • Sub-task
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 2.0-alpha3
    • jackrabbit-spi, JCR 2.0
    • None

    Description

      jcr2spi currently uses the JSR 170 way to determine whether a given Session owns the lock by checking of the lock token is null.
      with JSR 283 a new Lock method has been defined for this, while on the other hand the lock token is always null for session-scoped
      locks.

      In addition 283-locking allows to specify a timeout hint and hint about the owner info that should be displayed
      for information purpose.

      Proposed changes to SPI:

      • extend org.apache.jackrabbit.spi.LockInfo to cover the new functionality added with JSR 283
      • add an variant of RepositoryService.lock that allows to specify timeout and owner hint.

      Proposed changes to JCR2SPI:

      • change jcr2spi to make use of the new functionality and modify the test for session being lock holder.
        this mainly affects
        > LockOperation
        > LockManager impl
        > Lock impl

      Attachments

        1. JCR-2004-jcr-server.patch
          6 kB
          Angela Schreiber
        2. JCR-2004-jcr2spi.patch
          25 kB
          Angela Schreiber
        3. JCR-2004-sandbox.patch
          17 kB
          Angela Schreiber
        4. JCR-2004_spi.patch
          4 kB
          Angela Schreiber

        Issue Links

          Activity

            People

              angela Angela Schreiber
              angela Angela Schreiber
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: