You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Bilgin Ibryam <bi...@gmail.com> on 2011/11/28 14:57:33 UTC

Camel CMIS component

Hi all,

A week ago I submitted a camel-cmis component [1] but didn't described
it here, so here it is.

This component will allow Camel to connect to content
repositories(like Alfresco, SharePoint, OpenText) supporting CMIS
specification. It is a better alternative to camel-jcr component(which
actually can only create nodes) for accessing content repositories.

The consumer can retrieve content using CMIS queries (very similar to
SQL) or traverse the whole content tree from root to leaves.

The producer is capable of creating nodes on the server (folders, docs
and other node types) and also executing CMIS queries from the message
body.

The component is using another Apache project - OpenCMIS client
libraries from Apache Chemistry (also the in-memory-server from the
same project for unit tests).

Would be great if someone take a look at it and give some feedback if
any changes are needed in order to be committed to Camel.

BTW there are also two other components that I've submitted recently
and I think that will be useful for the Camel community, but don't see
much activity around them:

[2] camel-fop - for rendering pdf, png, svg and other formats
[3] camel-solr - for indexing documents into Apache Solr

Thanks,
Bilgin Ibryam


[1] https://issues.apache.org/jira/browse/CAMEL-4691
[2] https://issues.apache.org/jira/browse/CAMEL-3551
[3] https://issues.apache.org/jira/browse/CAMEL-4539

Re: Camel CMIS component

Posted by Bilgin Ibryam <bi...@gmail.com>.
On 28 November 2011 15:01, bvahdat <ba...@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.

Re: Camel CMIS component

Posted by bvahdat <ba...@swissonline.ch>.
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.

My questions are:

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

- 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.

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.

Re: Camel CMIS component

Posted by Bilgin Ibryam <bi...@gmail.com>.
@Boday, thanks for looking at camel-solr patch.

I also agree with Hadrian, the additional features to that component
can be added also later, once the basic version is committed, but
that's fine with me.

Thanks guys,
Bilgin


On 30 November 2011 13:52, Hadrian Zbarcea <hz...@gmail.com> wrote:
> Boday,
>
> After your review, if you consider that the code is acceptable with minor
> fixes, I'd suggest committing the patch *as is* and then add your fixes in a
> follow-up commit (unless the change is really, really minor). The reason is
> that the patch can that be tracked to the original author, who granted
> licence for inclusion for the particular patch he submitted.
>
> Cheers,
> Hadrian
>
>
>
> On 11/30/2011 02:26 AM, boday wrote:
>>
>> Bilgin, I'm still reviewing/enhancing the camel-solr component you
>> submitted.
>> I'm pretty close, just trying to add the necessary support to get it to
>> work
>> in osgi (karaf, etc).
>>
>>
>> Bilgin Ibryam wrote
>>>
>>>
>>> Hi all,
>>>
>>> A week ago I submitted a camel-cmis component [1] but didn't described
>>> it here, so here it is.
>>>
>>> This component will allow Camel to connect to content
>>> repositories(like Alfresco, SharePoint, OpenText) supporting CMIS
>>> specification. It is a better alternative to camel-jcr component(which
>>> actually can only create nodes) for accessing content repositories.
>>>
>>> The consumer can retrieve content using CMIS queries (very similar to
>>> SQL) or traverse the whole content tree from root to leaves.
>>>
>>> The producer is capable of creating nodes on the server (folders, docs
>>> and other node types) and also executing CMIS queries from the message
>>> body.
>>>
>>> The component is using another Apache project - OpenCMIS client
>>> libraries from Apache Chemistry (also the in-memory-server from the
>>> same project for unit tests).
>>>
>>> Would be great if someone take a look at it and give some feedback if
>>> any changes are needed in order to be committed to Camel.
>>>
>>> BTW there are also two other components that I've submitted recently
>>> and I think that will be useful for the Camel community, but don't see
>>> much activity around them:
>>>
>>> [2] camel-fop - for rendering pdf, png, svg and other formats
>>> [3] camel-solr - for indexing documents into Apache Solr
>>>
>>> Thanks,
>>> Bilgin Ibryam
>>>
>>>
>>> [1] https://issues.apache.org/jira/browse/CAMEL-4691
>>> [2] https://issues.apache.org/jira/browse/CAMEL-3551
>>> [3] https://issues.apache.org/jira/browse/CAMEL-4539
>>>
>>
>>
>> -----
>> Ben O'Day
>> IT Consultant -http://consulting-notes.com
>>
>> --
>> View this message in context:
>> http://camel.465427.n5.nabble.com/Camel-CMIS-component-tp5028929p5034788.html
>> Sent from the Camel Development mailing list archive at Nabble.com.
>
>
> --
> Hadrian Zbarcea
> Principal Software Architect
> Talend, Inc
> http://coders.talend.com/
> http://camelbot.blogspot.com/

Re: Camel CMIS component

Posted by Hadrian Zbarcea <hz...@gmail.com>.
Boday,

After your review, if you consider that the code is acceptable with 
minor fixes, I'd suggest committing the patch *as is* and then add your 
fixes in a follow-up commit (unless the change is really, really minor). 
The reason is that the patch can that be tracked to the original author, 
who granted licence for inclusion for the particular patch he submitted.

Cheers,
Hadrian


On 11/30/2011 02:26 AM, boday wrote:
> Bilgin, I'm still reviewing/enhancing the camel-solr component you submitted.
> I'm pretty close, just trying to add the necessary support to get it to work
> in osgi (karaf, etc).
>
>
> Bilgin Ibryam wrote
>>
>> Hi all,
>>
>> A week ago I submitted a camel-cmis component [1] but didn't described
>> it here, so here it is.
>>
>> This component will allow Camel to connect to content
>> repositories(like Alfresco, SharePoint, OpenText) supporting CMIS
>> specification. It is a better alternative to camel-jcr component(which
>> actually can only create nodes) for accessing content repositories.
>>
>> The consumer can retrieve content using CMIS queries (very similar to
>> SQL) or traverse the whole content tree from root to leaves.
>>
>> The producer is capable of creating nodes on the server (folders, docs
>> and other node types) and also executing CMIS queries from the message
>> body.
>>
>> The component is using another Apache project - OpenCMIS client
>> libraries from Apache Chemistry (also the in-memory-server from the
>> same project for unit tests).
>>
>> Would be great if someone take a look at it and give some feedback if
>> any changes are needed in order to be committed to Camel.
>>
>> BTW there are also two other components that I've submitted recently
>> and I think that will be useful for the Camel community, but don't see
>> much activity around them:
>>
>> [2] camel-fop - for rendering pdf, png, svg and other formats
>> [3] camel-solr - for indexing documents into Apache Solr
>>
>> Thanks,
>> Bilgin Ibryam
>>
>>
>> [1] https://issues.apache.org/jira/browse/CAMEL-4691
>> [2] https://issues.apache.org/jira/browse/CAMEL-3551
>> [3] https://issues.apache.org/jira/browse/CAMEL-4539
>>
>
>
> -----
> Ben O'Day
> IT Consultant -http://consulting-notes.com
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Camel-CMIS-component-tp5028929p5034788.html
> Sent from the Camel Development mailing list archive at Nabble.com.

-- 
Hadrian Zbarcea
Principal Software Architect
Talend, Inc
http://coders.talend.com/
http://camelbot.blogspot.com/

Re: Camel CMIS component

Posted by boday <be...@initekconsulting.com>.
Bilgin, I'm still reviewing/enhancing the camel-solr component you submitted. 
I'm pretty close, just trying to add the necessary support to get it to work
in osgi (karaf, etc).   


Bilgin Ibryam wrote
> 
> Hi all,
> 
> A week ago I submitted a camel-cmis component [1] but didn't described
> it here, so here it is.
> 
> This component will allow Camel to connect to content
> repositories(like Alfresco, SharePoint, OpenText) supporting CMIS
> specification. It is a better alternative to camel-jcr component(which
> actually can only create nodes) for accessing content repositories.
> 
> The consumer can retrieve content using CMIS queries (very similar to
> SQL) or traverse the whole content tree from root to leaves.
> 
> The producer is capable of creating nodes on the server (folders, docs
> and other node types) and also executing CMIS queries from the message
> body.
> 
> The component is using another Apache project - OpenCMIS client
> libraries from Apache Chemistry (also the in-memory-server from the
> same project for unit tests).
> 
> Would be great if someone take a look at it and give some feedback if
> any changes are needed in order to be committed to Camel.
> 
> BTW there are also two other components that I've submitted recently
> and I think that will be useful for the Camel community, but don't see
> much activity around them:
> 
> [2] camel-fop - for rendering pdf, png, svg and other formats
> [3] camel-solr - for indexing documents into Apache Solr
> 
> Thanks,
> Bilgin Ibryam
> 
> 
> [1] https://issues.apache.org/jira/browse/CAMEL-4691
> [2] https://issues.apache.org/jira/browse/CAMEL-3551
> [3] https://issues.apache.org/jira/browse/CAMEL-4539
> 


-----
Ben O'Day
IT Consultant -http://consulting-notes.com

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

Re: Camel CMIS component

Posted by Babak Vahdat <ba...@swissonline.ch>.
Hi Bilgin

Just awesome :-) Keep up the good job

Babak

Am 24.07.12 13:47 schrieb "Bilgin Ibryam" unter <bi...@gmail.com>:

>Just giving heads up: a cmis component is in trunk and here is a small
>blog
>entry on how to use it:
>
>http://www.ofbizian.com/2012/07/content-migration-with-camel-cmis.html
>
>Thanks
>Bilgin

Re: Camel CMIS component

Posted by Bilgin Ibryam <bi...@gmail.com>.
Just giving heads up: a cmis component is in trunk and here is a small blog
entry on how to use it:

http://www.ofbizian.com/2012/07/content-migration-with-camel-cmis.html

Thanks
Bilgin