camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bilgin Ibryam <bibr...@gmail.com>
Subject Re: Camel CMIS component
Date Thu, 01 Dec 2011 17:33:35 GMT
@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 <hzbarcea@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/

Mime
View raw message