jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-193) MultiStatus response for PROPPATCH (copied from JCR-175)
Date Thu, 15 Sep 2005 09:19:19 GMT
     [ http://issues.apache.org/jira/browse/JCR-193?page=all ]
angela resolved JCR-193:

    Resolution: Fixed


The method that sets and removes properties now returns a multistatus response object which
contains the individiual property states.
In addition modifyed the PROPPATCH so it now always returns a multistatus response (even if
the resource is locked), as it is required by the RFC (as far as i understood).

NOTE: with later change the nonowner-modify PROPATCH test of litmus 0.10.3 runs into an known
bug. If we experience problem with clients as will i will remove the code that catches the
DavExceptions and packs them into the mulitstatus (see also note in the code).

> MultiStatus response for PROPPATCH (copied from JCR-175)
> --------------------------------------------------------
>          Key: JCR-193
>          URL: http://issues.apache.org/jira/browse/JCR-193
>      Project: Jackrabbit
>         Type: Improvement
>     Reporter: angela
>     Assignee: angela
>     Priority: Minor

> Rob Owen commented on JCR-175:
> --------------------------------------------------
> doPropPatch in AbstractWebdavServlet still needs to send back a multistatus (207) response
even in the successful case.
> I didn't see a way to collect the success/failure status for each property, but instead
created a multistatus response and added a propstat (SC_OK) for each of the properties in
the setProperties and removeProperties. This allowed a WebDAV client, which expected a multistatus
response from PROPPATCH, to work correctly with jcr-server. In the more general case the actual
property status code will need to be used .

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message