[ http://issues.apache.org/jira/browse/JCR-400?page=all ]
angela resolved JCR-400:
------------------------
Fix Version: 1.0.1
Resolution: Fixed
Assign To: angela
issue has been fixed with rev. 397835, 398931
> PROPPATCH error marshalling when the resource can't be modified in general
> --------------------------------------------------------------------------
>
> Key: JCR-400
> URL: http://issues.apache.org/jira/browse/JCR-400
> Project: Jackrabbit
> Type: Bug
> Components: webdav
> Versions: 1.0
> Reporter: Julian Reschke
> Assignee: angela
> Priority: Minor
> Fix For: 1.0.1
> Attachments: diffs.txt
>
> Litmus test case "notowner_modify" (see
> <http://mail-archives.apache.org/mod_mbox/jackrabbit-dev/200604.mbox/[EMAIL
> PROTECTED]>) complains about a 423 (Locked) status code being sent back
> inside a 207 Multistatus:
> 9. notowner_modify....... WARNING: PROPPATCH failed with 0 not 423
> ...................... pass (with 1 warning)
> I think that warning is correct, as this is an error condition that doesn't
> need to be marshalled inside multistatus (1: it affects the resource at the
> Request URI and only that, 2: the operation failed completely). Let me also
> note that none of the other servers I tested with do return a 207 here (MS
> IIS, Apache/moddav, Xythos, SAP Netweaver KM),
> RFC2518bis will hopefully clarify error marshalling for PROPPATCH.
> From the source code, the current server behaviour is fully intentional (by
> specifically catching the DavException and using it in MultiStatus). Removing
> that code seems to fix the issue.
--
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
