hi there
may i?
the current situation is this:
- the servlets (also SimpleWebdavServlet) can handle PROPPATCH
- the call setProperty on the resource created before by the
resource-provider which can be set.
- the resources defines, how and if it handles setProperty calls.
- the DavResourceImpl in the simple packages does not allow
any property to be set, because i didn't need it so far and
because the 'nt:file' and 'nt:resource' nodes that are
displayed as non-collection resources do not allow for this.
no fancy reason otherwise.
it should be sufficient to create your own dav-resource.
if you have to extend the simple-servlet, there is probably
a bug... (btw: i did not make the effort to build a multistatus
in case of failure).
as far as i understood the rfc the server must understand
PROPPATCH in order to be dav 1 and 2 compliant. but its possible
that a given resource does not know any property to be set as
it is the case with the nt:file nodes.
regards
angela
Brian Moseley wrote:
Tobias Bocanegra wrote:
the default configuration of the import/export catalogs are in a
manner, that provide a more or less 'normal' fileserver. MKCOL creates
folders, PUT creates files. it is completely up to you to alter the
command chains for your purpose.
it's not that simple, tho. SimpleWebdavServlet and DavResourceImpl have
to be extended to translate the missing protocol stuff to jcr. and as
rob pointed out, new node types need to be defined that allow
user-defined properties.
even if it was as simple as adding new chain commands, clearly multiple
people want to have full webdav class 1 support. that should be
available in jcr-server, even if it's provided by an extension (tho i
don't see the purpose in that).
