Angela Schreiber wrote:
SHOULD :)
heh, gotcha :)
the name of the underlaying repository item cannot be altered, so i think its fine that PROPPATCH for this fails.
yeah, i understand. i have a use case in which the webdav resource name and display name need to be different, so pegging the display name to the jcr name doesn't work for me. but that's ok, i can provide my own node types.
i suggest to add all jcr-properties present on the underlaying resource to the set of dav-properties present on the resource and an attempt to call setProperty on the simple DavResource will try to set them... so it would be possible to use the PROPPATCH with the given implementation... i will do that.
i think that's a good compromise.
