Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Wed, 18 Jul 2012 08:49:34 +0000 (UTC)
From: "Bilgin Ibryam (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <1208476945.68254.1342601374898.JavaMail.jiratomcat@issues-vm>
In-Reply-To: 
 <433926695.38576.1321528011685.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (CAMEL-4691) New camel-cmis component
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CAMEL-4691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13416946#comment-13416946 ] 

Bilgin Ibryam commented on CAMEL-4691:
--------------------------------------

Sounds good, but is it good idea to commit code that fails the features validation?
                
> New camel-cmis component
> ------------------------
>
>                 Key: CAMEL-4691
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4691
>             Project: Camel
>          Issue Type: New Feature
>            Reporter: Bilgin Ibryam
>            Assignee: Bilgin Ibryam
>            Priority: Minor
>         Attachments: camel-cmis.patch, camel-cmis.patch, camel-cmis.patch
>
>
> A new component that would allow Camel to connect to content repositories(like Alfresco, SharePoint, OpenText) supporting CMIS specification. 
> This component can be an alternative to camel-jcr (which actually can only create node) for accessing content repositories.
> The consumer can retrieve content using CMIS queries (very similar to SQL) or traverse the content tree from root to leaves.
> The producer is capable of creating nodes on the server (folders, docs...) and also executing CMIS queries from the message body.
> It is using another Apache project - OpenCMIS client libraries from Apache Chemistry (also the in-memory-server from the same project for unit tests) 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira