[ http://issues.apache.org/jira/browse/JCR-405?page=all ]
Jukka Zitting updated JCR-405:
------------------------------
Version: 1.0
Merged for 1.0.1 in revision 409587.
About the API change: I'm accepting this in the patch release as the main API
in this case is the WebDAV PROPPATCH method, whose implementation is corrected
by this change. For now I consider the classes in jcr-server internal, so a
Java signature change is allowed. We may want to reconsider this approach if a
number of people are extending or otherwise depending on the code.
> PROPPATCH doesn't respect document order
> ----------------------------------------
>
> Key: JCR-405
> URL: http://issues.apache.org/jira/browse/JCR-405
> Project: Jackrabbit
> Type: Bug
> Components: webdav
> Versions: 1.0
> Reporter: Julian Reschke
> Assignee: angela
> Priority: Minor
> Fix For: 1.0.1
> Attachments: diffs.txt
>
> PROPPATCH is currently implemented in terms of
> DavResource.alterProperties(...), which takes a set of properties to be set
> and a set of properties to be removed. This is not sufficient to model
> WebDAV's method semantics, as the order in which set/remove instructions
> appear is supposed to be relevant.
> I have submitted a patch to the Litmus mailing list checking this (see
> <http://mailman.webdav.org/pipermail/litmus/2006-April/000196.html>).
> In jcr-server, alterProperties probably should be changed to take an
> (ordered) list of set/remove instructions instead. The simplest approach for
> that would probably be to use a List containing either DavProperty (set) or
> DavPropertyName (remove) objects.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
