jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dominique Pfister" <dominique.pfis...@day.com>
Subject Re: jcr-cmis sandbox
Date Tue, 02 Dec 2008 13:15:34 GMT
Hi Julian,

On Tue, Dec 2, 2008 at 12:59 PM, Julian Reschke <julian.reschke@gmx.de> wrote:
> Dominique Pfister wrote:
>>
>> Hi,
>>
>> After having had a first look at the CMIS specification, I decided to
>> start off with the jcr-cmis implementation. I therefore created a
>> jcr-cmis sandbox with the following initial structure:
>>
>> jcr-cmis
>> -- + server
>> ---- + rest
>> ---- + ws
>>
>> I intend to start working on the server/rest subtree (where the REST
>> API binding will reside). Any comment/feedback and - even better :) -
>> any contribution/participation on the the server/ws subtree
>> (containing the Web Services Binding) are more than welcome!
>
> I guess it'll be harder to find volunteers for the ws part :-)
>
> Two thoughts:
>
> 1) At some point of time, we'll have to define a mapping from CMIS to JCR
> (relatively simple) *and* the other way around (now that's harder). So, how
> to map identifiers (types, paths), what to do with the CMIS relation objects
> and so on. Should we start a design document (a text file) for that, or
> would a Wiki work better?

That's a good point. It makes no sense to have both bindings - REST
and SOAP - translate their calls into JCR API, but rather have a
generic CMIS to JCR adapter that can be plugged into either of the two
binding implementations.

>
> 2) I think that having a separate connector for CMIS in addition to WebDAV
> should be avoided. We essentially would mint different HTTP URLs for the
> same thing. So maybe not now, but at a later point of time it would be good
> if we could merge the new functionality into the existing WebDAV stack.

Hm, I'm not sure about the two things being actually the same: looking
at CMIS' REST binding, I see custom headers (e.g. CMIS-type), special
content types (e.g. application/atom+xml) and a HTTP body consisting
of XML documents with root elements other than "DAV:". I'm not
familiar with the extensibility of the WebDAV connector, so I'll just
have to ask, whether you think that this is still inside the scope of
the WebDAV connector?

Dominique

>
> BR, Julian
>

Mime
View raw message