[
https://issues.apache.org/jira/browse/SLING-4318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14281422#comment-14281422
]
Tomek Rękawek commented on SLING-4318:
--------------------------------------
We could definitely use version label or version number every time we need to
specify a version (eg. in the {{;v="1.0"}} or {{;v="myLabel").
I think it's also possible to create a RESTful API to manage (create and
remove) activities. The {{setActivity()}} operation which is crucial here works
on the current session which is created and closed during the request, so we
can't make it a separate REST operation. Rather than that we could add new
parameter (eg. {{:activity=xyz}}) which could be used with all POSTs modifying
the checked out node, so Sling will set the activity before making changes.
The last thing - list of content modified between versions - seems to be an
feature built on the versioning API rather than the API operation itself. I
think it's too specific to put it in the RESTful API, as there is no similar
operation in the JCR VersionManager.
> Sling resource API does not expose any versioning features - bounty offered.
> ----------------------------------------------------------------------------
>
> Key: SLING-4318
> URL: https://issues.apache.org/jira/browse/SLING-4318
> Project: Sling
> Issue Type: New Feature
> Components: Documentation, JCR, Servlets
> Affects Versions: Servlets Resolver 2.3.8
> Environment: N/A
> Reporter: Bruce Edge
> Labels: api, crud, servlet-api, versioning, versions
>
> The javax.jcr.version.VersionManager is not exposed in the sling resource API:
> http://thread.gmane.org/gmane.comp.apache.sling.user/1610
> My company is interested in paying for this development. Please contact if
> interested.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
