From commits-return-6945-apmail-jackrabbit-commits-archive=jackrabbit.apache.org@jackrabbit.apache.org Sun Jan 25 17:20:00 2009 Return-Path: Delivered-To: apmail-jackrabbit-commits-archive@www.apache.org Received: (qmail 54732 invoked from network); 25 Jan 2009 17:19:58 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 25 Jan 2009 17:19:58 -0000 Received: (qmail 11171 invoked by uid 500); 25 Jan 2009 17:19:58 -0000 Delivered-To: apmail-jackrabbit-commits-archive@jackrabbit.apache.org Received: (qmail 11135 invoked by uid 500); 25 Jan 2009 17:19:58 -0000 Mailing-List: contact commits-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list commits@jackrabbit.apache.org Received: (qmail 11126 invoked by uid 99); 25 Jan 2009 17:19:58 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 25 Jan 2009 09:19:58 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.130] (HELO eos.apache.org) (140.211.11.130) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 25 Jan 2009 17:19:47 +0000 Received: from eos.apache.org (localhost [127.0.0.1]) by eos.apache.org (Postfix) with ESMTP id 3977C118D7 for ; Sun, 25 Jan 2009 17:19:26 +0000 (GMT) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Apache Wiki To: commits@jackrabbit.apache.org Date: Sun, 25 Jan 2009 17:19:26 -0000 Message-ID: <20090125171926.15537.17151@eos.apache.org> Subject: [Jackrabbit Wiki] Update of "SandboxCMIS" by DavidNuescheler X-Virus-Checked: Checked by ClamAV on apache.org Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jackrabbit Wiki" for change notification. The following page has been changed by DavidNuescheler: http://wiki.apache.org/jackrabbit/SandboxCMIS The comment on the change is: Initial CMIS Sandbox Description New page: === What is CMIS? === CMIS stands for Content Manegement Interoperability Services and consists mainly of two network bindings for essential Document Management operations. CMIS is in the process of being developed at [http://xml.coverpages.org/cmis.html OASIS]. === The CMIS Sandbox at Jackrabbit === Based on interest from various Apache Communities the CMIS Sandbox is hosted by the Apache Jackrabbit project and is open to all committers of the ASF. Sumamrizing conversations on the dev mailing list the goal of this effort would be to build a freely available implementation and client of the CMIS specification as it grows. While the CMIS specification is still under development the early implementation will allow to give feedback to the Technical Committee at OASIS to modify and improve the specification. The implementation should not need any Jackrabbit (Content Repository) specific dependencies but should be as portable and reusable for other implementations as possible. === Overall Proposed Architecture === The overall Architecture is separated into three major blocks as reflected in the [http://svn.apache.org/repos/asf/jackrabbit/sandbox/jcr-cmis/ SVN Layout]. The API represents the Java Language Bindings of the CMIS Model and therefore is used to implement both the CMIS client (that exposes the API) but also the server that allows for plug-able implementation of that. === Proposed Server Architecture === The CMIS Server is architected in a fashion that offers a Layered approach. The AtomPub and SOAP bindings are separated by the API. This allows to use both protocol implementations while just having to implement the API on any particular proprietary or standard based server. In Jackrabbit the implementation of the API then will use a standards based JCR binding to avoid and Jackrabbit specific bindings and hence allows to be run on any third party JCR implementation. === Proposed Client Architecture === To provide a general purpose CMIS Java client it is important of course provide language bindings of the CMIS Model and then implement the two protocols proposed by CMIS. This will not only be used by Java Application Developers that want to consume CMIS but also can serve as an initial test suite to test any servers interoperability. === First Steps with the CMIS Server === (To be added) === First Steps with the CMIS Client === (To be added) === Further Conversations === Find the current CMIS Discussions on the [http://jackrabbit.markmail.org/search/?q=cmis Jackrabbit] List and also on the CMIS [http://markmail.org/search/?q=list%3Aorg.oasis-open.lists.cmis OASIS] list.