Julian,
as I pointed out before, my source provides just "glue code" to build WebDAV
based RESTful WebServices easily, just as JAX-RS provides just "glue code"
to build HTTP based services. It is a great idea to have an SPI to attach
JCR-enabled backends, but this is something that is not part of my current
source, so you and Daniel could provide this ontop if you like (what would
be great).
Regards
Markus
But I think that the WebDAV for Jersey should not use the JCR. It should
implement the WebDAV-Methods and Features and should not point to a special
api. I want to use this WebDAV feature for a lot of things. And there is
still a WebDAV implementation for the JCR. So why should this project use
JCR? I also know the talks about the CMIS and this is not the list for it.
:)
It would be really cool if there would be generic solution which we could
map to a lot of things/apis. (JCR too) Maybe, something like the SPI of the
Jackrabbit.