[
https://issues.apache.org/jira/browse/JCR-1348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14378146#comment-14378146
]
Stefan Thieme commented on JCR-1348:
------------------------------------
I have described a versioning workflow using curl on the following website:
http://stackoverflow.com/questions/10571902/versioning-jcr-nodes-via-dav-howto/29238421
Though this is specifically mimicking a Microsoft Office session the basic
CHECKIN/CHECKOUT version workflow is easily visible.
I hope this is helpful in testing auto-version capabilities.
> simple-webdav: DAV:auto-version property not handled properly
> -------------------------------------------------------------
>
> Key: JCR-1348
> URL: https://issues.apache.org/jira/browse/JCR-1348
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-jcr-server
> Reporter: angela
>
> rfc 3253 defines the effect of the DAV:auto-version property ([1], [2]).
> the version-support implemented in the simple server adds the auto-version
> property to the property-list but does
> - not prohibit changing the value (which currently would be the correct)
> - nor behave properly if the value is modified (auto-version not yet
> implemented)
> - nor does it check if the prop-value is valid.
> [1] http://www.webdav.org/specs/rfc3253.html#rfc.section.2.2.2
> [2] http://www.webdav.org/specs/rfc3253.html#PROPERTY_auto-version
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
