Return-Path: X-Original-To: apmail-camel-dev-archive@www.apache.org Delivered-To: apmail-camel-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1E15E913D for ; Wed, 30 Nov 2011 07:26:53 +0000 (UTC) Received: (qmail 77626 invoked by uid 500); 30 Nov 2011 07:26:51 -0000 Delivered-To: apmail-camel-dev-archive@camel.apache.org Received: (qmail 77495 invoked by uid 500); 30 Nov 2011 07:26:39 -0000 Mailing-List: contact dev-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list dev@camel.apache.org Received: (qmail 77476 invoked by uid 99); 30 Nov 2011 07:26:37 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Nov 2011 07:26:37 +0000 X-ASF-Spam-Status: No, hits=2.0 required=5.0 tests=SPF_NEUTRAL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Nov 2011 07:26:30 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1RVeYS-0005TK-Ti for dev@camel.apache.org; Tue, 29 Nov 2011 23:26:08 -0800 Date: Tue, 29 Nov 2011 23:26:08 -0800 (PST) From: boday To: dev@camel.apache.org Message-ID: <1322637968915-5034788.post@n5.nabble.com> In-Reply-To: References: Subject: Re: Camel CMIS component MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org 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.