angela (JIRA) wrote:
[ https://issues.apache.org/jira/browse/JCR-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513525 ]
angela commented on JCR-388:
----------------------------
so... had a look at the changes and i found the following things. i already
started modifying the patch a bit, so there is no need for a new one. just for
the record:
- DeltaVResourceImpl: compliance class should from my point of view also
mention the Label feature
Angela, please keep in mind that the Label *header* is deprecated,
please do not implement it (see <http://www.webdav.org/deltav/>).
...
RFC 3253 defines a separate behaviour for version-controlled collections. However the current approach
does not take into account whether a resource represents a collection or not. As soon as the corresponding
repository node is of type mix:versionable the resource is exposed to be
versionable as well. If we want
to make the simple server to be compliant to RFC 3253 this should be addressed.
...
I'm not completely sure what the issue is? A version controlled
collection is a specific type of a regular version controlled resource,
it just also records information about version controlled children...
..
Best regards, Julian
