Julian,
> I mean a WebDAV implementation that uses the JCR API for storage.
I see. That could be one thing that could be built using my contribution.
> And yes, I do except "them" to finish it, given the fact that I'm a
> member of that Expert Group, and we're really in the process of closing
> the last issues.
Daniel, isn't that what you are waiting for?
> So, rephrasing this into a question instead: would that WebDAV
> implementation be targeted to a specific storage API (like file system
My contribution first of all "just" covers the extension of Jersey to
provide not only HTTP headers and result codes, but also WebDAV header,
result codes and JAXB elements. That means, using my contribution provides
the same stuff for WebDAV (plus JAXB elements for the standardized WebDAV
request and response bodies) that JSR-311 provides for HTTP.
It would be an interesting idea to add more or less ready-to-use backends
for different storage systems. For example, I could imagine at least three
types of backends that would make sense: (a) Files System, (b) JPA, (c) JCR.
Maybe this is a good split point in the project: While some (like me) are
working on the "pure" WebDAV stuff, others (like you) could concentrate on
the bindings to specific APIs. I did not think about this before, but your
idea is just great. With such a ready-made JCR backend, one could easily
build a WebDAV interface to any CMS/DMS. Cool. Let's do that! :-)
Regards
Markus