Uploaded image for project: 'Sling'
  1. Sling
  2. SLING-848

Support getting versioned resources by using uri path parameters

    Details

      Description

      Getting versioned content should be support thorough uri path parameters, like /something/hello;v=1.1
      For jcr based resources the value of the version should either point to a version name or label.

      In order to not change our existing apis, we introduce a new utility method which removes all uri path parameters
      and returns a map of these. Every resource provider could use this utility method and then decide to act on these
      parameters.
      If a requested version does not exists, a 404 is returned.
      If the requested node does not directly point to a versionable node, the algorithm checks the parent hierarchy until a versionable node is found, and tries to get the version of this node and then goes down the path again. If the versionable node does not have the requested version or the child, a 404 is returned.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                tomek.rekawek Tomek Rękawek
                Reporter:
                cziegeler Carsten Ziegeler
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: