Return-Path: Delivered-To: apmail-jackrabbit-commits-archive@www.apache.org Received: (qmail 92417 invoked from network); 3 Mar 2008 20:52:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Mar 2008 20:52:16 -0000 Received: (qmail 78913 invoked by uid 500); 3 Mar 2008 20:52:12 -0000 Delivered-To: apmail-jackrabbit-commits-archive@jackrabbit.apache.org Received: (qmail 78888 invoked by uid 500); 3 Mar 2008 20:52:12 -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 78879 invoked by uid 99); 3 Mar 2008 20:52:12 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Mar 2008 12:52:12 -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.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Mar 2008 20:51:37 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 94766234C089 for ; Mon, 3 Mar 2008 12:51:00 -0800 (PST) Message-ID: <1259234956.1204577460606.JavaMail.www-data@brutus> Date: Mon, 3 Mar 2008 12:51:00 -0800 (PST) From: confluence@apache.org To: commits@jackrabbit.apache.org Subject: [CONF] Apache Jackrabbit: Object Content Mapping (page edited) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Object Content Mapping (JCR) edited by Christophe Lombart Page: http://cwiki.apache.org/confluence/display/JCR/Object+Content+Mapping Changes: http://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=75348&originalVersion=7&revisedVersion=8 Comment: --------------------------------------------------------------------- Add a entry for the new tutorial Change summary: --------------------------------------------------------------------- Add a entry for the new tutorial Change summary: --------------------------------------------------------------------- Add a entry for the new tutorial Change summary: --------------------------------------------------------------------- Add a entry for the new tutorial Change summary: --------------------------------------------------------------------- Add a entry for the new tutorial Content: --------------------------------------------------------------------- {warning:title=Warning} The Jackrabbit OCM documentation is still in progress. We advise you also to review [the unit tests|http://svn.apache.org/viewvc/jackrabbit/trunk/jackrabbit-ocm/src/test/]to get an overview on current OCM features. {warning} * [Object Content Manager] ** [Basic OCM operations] ** [OCM Search] ** [OCM Version Management] ** [OCM Locking] * Tutorials ** [5' with Jackrabbit OCM] ** [A simple OCM project with Maven & Eclipse] * [Mapping Stategies] (obsolete doc) ** [Mapping Atomic Fields] (obsolete doc) ** [Mapping Bean Fields] (obsolete doc) ** [Mapping Collection Fields] (obsolete doc) ** [Advanced Mapping Strategies] (obsolete doc) Jackrabbit OCM is a framework used to persist java objects (pojos) in a JCR repository including association, inheritance, polymorphism, composition, and the Java collections framework. It offers also features like version support, object locking and express queries with Java-based criteria, as well as with JCR query languages. In order to easily support the JCR specification, any content application managing an high level object model can use this framework. For example, a classic Forum application contains objects like "Forum", "Topic" and "Post". Now, the data objects (pojo) can be managed by our JCR mapping tools in order to persist them into a JCR compliant repository. h2. Why an ocm? The object content mapping framework was created for the following different reasons: * Sometimes it is very convenient to be able to just access the JCR nodes and properties directly from your presentation-layer for very simple things (mostly generic display). When a lot of "business logic" are involved, the JCR API can be too low level and real business objects (pojo) are more appreciate in such cases. * The OCM framework provides more abstraction on the technologies used to persist your content. The different application layers are less dependent on the JCR API. * ORM tools like OJB or Hibernate are not appropriate for content oriented application. h2. Prerequisite Before using this OCM framework, you should review the JCR specification and implementations like Apache Jackrabbit. --------------------------------------------------------------------- CONFLUENCE INFORMATION This message is automatically generated by Confluence Unsubscribe or edit your notifications preferences http://cwiki.apache.org/confluence/users/viewnotifications.action If you think it was sent incorrectly contact one of the administrators http://cwiki.apache.org/confluence/administrators.action If you want more information on Confluence, or have a bug to report see http://www.atlassian.com/software/confluence