Angela Schreiber wrote:
hi
the latest commits to the jcr-server cover the following
issues with the 'simple' servlet:
1) ETags (http://issues.apache.org/jira/browse/JCR-174)
-----------------------------------------------------------
discussion:
http://www.mail-archive.com/[email protected]/msg01505.html
- Calculation of the ETag is removed from NodeResource and
delegated to the Export-Commands
- accordingly the getStrongEtag method on NodeResource does
not make sense and has been removed.
- in addition: if a strong etag is present on a resource
its now used in the evaluation of the IF header (there used
to be a //todo in the WebdavRequestImpl).
2) Proppatch (http://issues.apache.org/jira/browse/JCR-175)
------------------------------------------------------------
discussion:
http://www.mail-archive.com/jackrabbit-dev%40incubator.apache.org/msg01971.html
- Simple-DavResource now exposes jcr-Properties present
on the node that represents the dav-resource.
- Proppatch is forwarded to the corresponding jcr-Properties
instead of throwing Method-Not-Allowed
- namespace prefixes present with jcr-property names
are remapped if they would conflict with any of the
namespaces predefined with the webdav library (basically
the DAV: namespace and the jcr-webdav namespace defined
for the observation and transaction extensions).
3) Resource-Filter
------------------------------------------------------------
- allows to filter resources by namespace and nodetype
(initial version)
- currently respected with PROPFIND and with any write
methods (in order to avoid creation of resources that
will not be visible later on).
- Drawback: the exports-command are not aware of the filter
yet.
> see discussion regarding the command-chains in general
> see also http://issues.apache.org/jira/browse/JCR-165)
Angela, great stuff.
What is the status of the WebDAV litmus tests at this point?
--
Stefano.
