++ This bug is a clone of bug 780107 ++ Affects: Release Notes project_key: SOA I was unable to update or set new property on ModeShape resource through WebDav interface. I used PROPPATCH verb to create new property on previously created resource in Modeshape, the property was created (WebDav server returned 200 OK status code) then I retrieved all properties on this resource - I expected newly created property to be there, but it wasn't.
Link: Added: This issue depends MODE-985
Link: Added: This issue is related to MODE-984
Link: Added: This issue depends MODE-984
Candidate for SOA 5.1.0
We will try to have this fixed, but if we are unable, it will need to be part of the release notes (thus RN flag set).
Affects: Added: [Release Notes]
*** Bug 780107 has been marked as a duplicate of this bug. ***
Horia Chiorean <hchiorea> made a comment on jira MODE-984 Bumped up the priority, because there is a BZ attached.
Horia Chiorean <hchiorea> made a comment on jira MODE-984 Implemented generic WebDAV PROPPATCH support and updated PROPFIND to use custom properties. Also, the JCR extension of WebDAV was updated to be able to set & retrieve custom properties on nodes. *NOTE*: in the attached example/test case the correct behavior is/should've been an exception, because by default folders are of type {{nt:folder}} and files are of type {{nt:file}}, *neither of which* support custom properties in JCR.
Randall Hauch <rhauch> made a comment on jira MODE-984 Merged into the 'master' branch, and cherry-picked into the '3.3.x' branch.
Randall Hauch <rhauch> updated the status of jira MODE-984 to Closed
Documented in Release Notes as a new feature.