Hi Julian,
I hope too that we get the JSR283 finish, because my company is also in the
group and we are implementing it into our system.
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.
:)
So let's have a look what we can do with the source from Mark.
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.
Best Regards,
Daniel
2008/12/6 Julian Reschke <julian.reschke_at_gmx.de>
> Markus KARG wrote:
>
>> Julian,
>>
>> great to have your support. I'm planning to publish first stuff in my
>> winter
>> break (have to tidy up my source first...). Stay tuned. :-) Just waiting
>> for
>> the Jersey Heads to tell me whether it shall be part of Jersey or not.
>>
>> BTW, can you give me a short abstract of the idea of JSR-283? I have no
>> real
>> idea what a "Content Repository API" is... Is that something like a common
>> interface ("driver") to any kind of document management system?
>>
>> Thanks
>> Markus
>>
>
> Essentially, if you would define a generic Java API to a document system
> supporting WebDAV and all it's extensions, you would likely come up with an
> API very similar to JCR. You may want to have a look at Apache Jackrabbit's
> (*) WebDAV servlet.
>
> BR, Julian
>
> (*) Apache Jackrabbit is the reference implementation of JCR 1.0 (JSR-170).
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: dev-help_at_jersey.dev.java.net
>
>
--
Mit freundlichen Grüßen
Daniel Manzke