[ http://issues.apache.org/jira/browse/JCR-405?page=comments#action_12376010 ]
Julian Reschke commented on JCR-405: ------------------------------------ Sorry, forgot to mention that this change is *not* well tested yet (I've verified in the debugger that the code executes as designed, but I currently don't have a setup with a repository where property modifications are actually supported). > PROPPATCH doesn't respect document order > ---------------------------------------- > > Key: JCR-405 > URL: http://issues.apache.org/jira/browse/JCR-405 > Project: Jackrabbit > Type: Bug > Components: webdav > Reporter: Julian Reschke > Priority: Minor > 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
