You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2007/07/19 16:05:06 UTC
[jira] Issue Comment Edited: (JCR-388) add support for RFC 3253 to
the simple server
[ https://issues.apache.org/jira/browse/JCR-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513897 ]
angela edited comment on JCR-388 at 7/19/07 7:05 AM:
-----------------------------------------------------
i will attach my patch, where i (hopefully) integrated all comments (see jira). during
some quick testing in found a couple of additional things:
- compliance class: version-history was missing as well
- DAV:predecessor-set missing with checked-out vc-resource
- in response to the discussion with julian i disabled
the version-control feature for collections.
-> versions are always non-collection resources
-> versions never expose any member resources
-> isCollection() always returns false
-> the locator for versions has to be build accordingly
-> collections may never put under DAV version control.
- VersionResources are read-only -> override addMember, removeMember and all methods related
to PROPPATCH.
- VersionHistoryResource are read-only except for remove of versions (i'm not sure, whether this is
allowed with deltaV. it is optional in JCR).
- VersionHistoryResource did only specify version-history resource type. it should
also include 'collection'.
- there were some more comments that were copied from jcr-server without making sense in the new context.
- VersionHandler: i change the behaviour in order not to export all jcr properties present with the content-node
such as the DefaultHandler does.
was:
i will attach my patch, where i (hopefully) integrated all comments (see jira). during
some quick testing in found a couple of additional things:
- compliance class: version-history was missing as well
- DAV:predecessor-set missing with checked-out vc-resource
- in response to the discussion with julian i disabled
the version-control feature for collections.
-> versions are always non-collection resources
-> versions never expose any member resources
-> isCollection() always returns false
-> the locator for versions has to be build accordingly
-> collections may never put under DAV version control.
- VersionResources are read-only -> override addMember, removeMember and all methods related
to PROPPATCH.
- VersionHistoryResource are read-only except for remove of versions (i'm not sure, whether this is
allowed with deltaV. it is optional in JCR).
- there were some more comments that were copied from jcr-server without making sense in the new context.
- VersionHandler: i change the behaviour in order not to export all jcr properties present with the content-node
such as the DefaultHandler does.
> add support for RFC 3253 to the simple server
> ---------------------------------------------
>
> Key: JCR-388
> URL: https://issues.apache.org/jira/browse/JCR-388
> Project: Jackrabbit
> Issue Type: New Feature
> Components: webdav
> Affects Versions: 0.9
> Reporter: jeremi Joslin
> Assignee: angela
> Priority: Minor
> Attachments: JCR-388_2007_07_19.patch, patch_16JUL07.txt, patch_16JUL07.zip, patch_rfc3253.zip, Review.txt, rfc.zip
>
>
> http://www.ietf.org/rfc/rfc3253.txt
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.