[jira] Commented: (JCR-405) PROPPATCH doesn't respect document order

["angela (JIRA)" <ji...@apache.org>]

    [ http://issues.apache.org/jira/browse/JCR-405?page=comments#action_12375133 ] 

angela commented on JCR-405:
----------------------------

(second try, sorry if the first comment made it anyway to jira)

this would required the following api methods to be change or - perhaps better - deprecated/replaced:

- DavResource#alterProperties
  > method signature
  > ev. mark deprecated and add improved alterProperties method

- DavServerRequest#getPropPatchRemoveProperties
- DavServerRequest#getPropPatchSetProperties
  > merged to a single method that returns list of sets and removals
  > ev. rather mark those methods deprecated and add improved method.

is there a policy how to handle api changes between releases?
i had a lot of troubles with jdom and compatibility issues and would wish to avoid such annoyance within jcr-server.

regards
angela

> 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

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