On 28 November 2011 15:01, bvahdat <babak.vah...@swissonline.ch> wrote:
> Hi Bilgin,
>
> had a chance to look at your camel-cmis component (BTW another nice code of
> yours). I'm a newbie to JSR-283 and don't know much about it's API, however
> probably I'm going to be involved in a Sharepoint-Integration project and
> that would be really cool if I could just kick the Sharepoint repository
> through Apache Camel's own cmis producer/consumer.

hopefully you it will be soon (if someone takes the initiative for
this component)

>
> My questions are:
>
> - If there's any Pro/Contra between OpenCMIS and Jackrabbit and what was
> your motivation not to use the latter.

Before creating the cmis component I helped for updating the camel-jcr
component from v1 to v2 and noticed that it is really a basic
implementation (only a producer that can create nodes on the
repository). The cmis component in addition can also query using the
producer or consumer.

Therea are many comparisons between cmis and jcr, but I prefer the one
that says they are complementary, jcr specifies a java API while cmis
two protocol bindings, similar to Servlet API and HTTP protocol.

Apache Chemistry/OpenCMIS makes every JCR complient repository (like
Jackrabbit) also CMIS complient, so you can continue using the same
repository after the switch from jcr to cmis.

>
> - Is there anything (in the sense of the CRUD operations) one could not make
> it work through JCR-API pushed into Sharepoint, so that we should stuck to
> Sharepoint's own GUI / Tools.
>

I'm not familiar with Sharepoint, but each content repository supports
different subset of CMIS capabilities. You have to check whether
Sharepoint supported capabilities are enough for your integration
task. (Another good thing about CMIS is that checking/retriving the
supported capabilities is also part of the spec)

HTH
Bilgin

> Eyvallah Kardes :-)
>
> Babak
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/Camel-CMIS-component-tp5028929p5029099.html
> Sent from the Camel Development mailing list archive at Nabble.com.

Reply via email to