[
https://issues.apache.org/jira/browse/SLING-4318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14281006#comment-14281006
]
Bruce Edge commented on SLING-4318:
-----------------------------------
Would it be possible to use nt:activity and/or nt:versionLabels as version
specifiers for retrieving content as well as parameters to POST operations such
that an automated operations that commit a large number of new files could
create an activity and then pass the activity name and/or a versionLabel as
parameters to all POST operations which would apply the activity and
versionLabel to the JCR update?
I expect this would add complexity to the API. Will defer to more experienced
members as to whether this is viable. Any mechanism to group sets of changes as
well as tag versions would be great.
Another use case we have is to get a list of modified content between versions
of a base node. Ideally we could get a json array of modified/new content in a
tree branch specified by a base path and two versions specified by label.
Again, open to suggestions, these are ideas carried over from other domains
that may or may not map directly into the sling/JCR world.
> 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)
