Angela Schreiber wrote:
Julian Reschke wrote:
Angela Schreiber wrote:
What's that for? Why not simply create an empty, locked, resource?
because from my understanding the null-resource does
not exist and it would look wrong to me, if it
was created upon the LOCK request... at least
But that's what the spec explicitly allows to do.
up to now i wouldn't know how to define 'empty'. in
case of nt:file node: i can't omit the jcr:content node.
So it would contain a jcr:content node with a jcr:data property of length 0.
and if jcr:content is nt:resource i couldn't omit the
the jcr:data prop...
That's fine.
and if it's there i would expect a HEAD/GET request not
to return not-found.
Which is fine as well. See
<http://greenbytes.de/tech/webdav/rfc4918.html#lock-unmapped-urls>.
BR, Julian
