You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Stefan Thieme (JIRA)" <ji...@apache.org> on 2015/05/05 10:51:07 UTC

[jira] [Commented] (JCR-1348) simple-webdav: DAV:auto-version property not handled properly

    [ https://issues.apache.org/jira/browse/JCR-1348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14528134#comment-14528134 ] 

Stefan Thieme commented on JCR-1348:
------------------------------------

Angela,

I am adding your thoughts you have given in response to "file issues on webdav" on the users mailing list, as this is related.

http://jackrabbit.markmail.org/message/7qgliawhouiz4ee6?q=auto-version+list:org.apache.jackrabbit.users#query:auto-version%20list%3Aorg.apache.jackrabbit.users+page:1+mid:7qgliawhouiz4ee6+state:results

Angela wrote Oct 21, 2008 7:26:44 am:
sure. there are some thoughts in the issue regarding
the resolution.
some prerequisites i didn't mention: in order to be able
to set custom properties on a webdav resource the underlying
jcr file node must not have it's jcr:content node being
nt:resource (by default it's nt:unstructured in the simple
dav server).

further more: if the DAV:auto-version property was
present in the JCR repository, performing the automated
checkout/checkin or lock/unlock could be done in the
handlers for resource updates/creation.

but note, that this is just a rough guideline. i didn't
carefully think about all the details of the implementation.

> 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)