Details

      Activity

      Hide
      angela added a comment -

      Revision: 918491 [work in progress]

      spi:

      • activity aware variant of Repository.checkpoint (-> analogue to checkout)

      jcr2spi:

      • change VersionManager.checkpoint accordingly and take current activity into account.
      Show
      angela added a comment - Revision: 918491 [work in progress] spi: activity aware variant of Repository.checkpoint (-> analogue to checkout) jcr2spi: change VersionManager.checkpoint accordingly and take current activity into account.
      Hide
      angela added a comment - - edited

      Revision: 916278 [work in progress, tested using jcr2dav-ConformanceTest]

      jcr2spi:

      • simplify VersionManager.checkpoint if Node is already checkedin

      spi2dav + server-side implementation in jcr-server

      • implement checkpoint as separate checkin-checkout [tmp. solution]
      • implement shallow merge using custom extension of the MERGE request body [DAV:depth element]

      spi2dav : bug fixes

      • merge (besteffort <-> DAV:no-auto-merge)
      • restore (nodeId may point to non-existing node -> extract existing parent + relPath

      server-side:

      • fix bug in server-side merge. for 1:1 remoting the MERGE response body should list the failed ids instead of the affected
        resource [DeltaV specified behaviour that doesn't make sense for remoting over SPI]
      • fix bug in restore with relPath
      Show
      angela added a comment - - edited Revision: 916278 [work in progress, tested using jcr2dav-ConformanceTest] jcr2spi: simplify VersionManager.checkpoint if Node is already checkedin spi2dav + server-side implementation in jcr-server implement checkpoint as separate checkin-checkout [tmp. solution] implement shallow merge using custom extension of the MERGE request body [DAV:depth element] spi2dav : bug fixes merge (besteffort <-> DAV:no-auto-merge) restore (nodeId may point to non-existing node -> extract existing parent + relPath server-side: fix bug in server-side merge. for 1:1 remoting the MERGE response body should list the failed ids instead of the affected resource [DeltaV specified behaviour that doesn't make sense for remoting over SPI] fix bug in restore with relPath
      Hide
      Marcel Reutegger added a comment -

      I suggest we complete that work after the 2.0 release.

      Show
      Marcel Reutegger added a comment - I suggest we complete that work after the 2.0 release.
      Hide
      angela added a comment -

      activity, configuration impl in jcr2spi and spi level.

      • but full versioning not yet implemented in all spi impls.
      • some tests still failing -> see spi2jcr pom.xml
      Show
      angela added a comment - activity, configuration impl in jcr2spi and spi level. but full versioning not yet implemented in all spi impls. some tests still failing -> see spi2jcr pom.xml
      Hide
      angela added a comment -

      Changes to JCR 2 SPI

      • VersionManager implementation
      • new methods with VersionHistory
      • new methods with Version

      Change to SPI:

      • RepositoryService.checkpoint
      • RepositoryService.merge (for shallow merge)

      TODO both in JCR2SPI and SPI:

      • Activity
      • Configuration
      Show
      angela added a comment - Changes to JCR 2 SPI VersionManager implementation new methods with VersionHistory new methods with Version Change to SPI: RepositoryService.checkpoint RepositoryService.merge (for shallow merge) TODO both in JCR2SPI and SPI: Activity Configuration

        People

        • Assignee:
          Unassigned
          Reporter:
          angela
        • Votes:
          0 Vote for this issue
          Watchers:
          2 Start watching this issue

          Dates

          • Created:
            Updated:

            Development