Mailing-List: contact commits-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Apache Wiki <wikidiffs@apache.org>
To: commits@jackrabbit.apache.org
Date: Mon, 16 Jun 2008 09:23:13 -0000
Message-ID: <20080616092313.8755.59432@eos.apache.org>
Subject: [Jackrabbit Wiki] Update of "JcrSpecImplementation" by
 AlexanderKlimetschek

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 AlexanderKlimetschek:
http://wiki.apache.org/jackrabbit/JcrSpecImplementation

New page:
Jackrabbit in general is a fully JCR-1.0-compliant ([http://jcp.org/en/jsr/detail?id=170 JSR-170]) Java content repository implementation. As the spec does not mandate every detail, Jackrabbit has to use a specific implementation in some cases and it also contains some additional features. This page shall give an overview.

'''Please note''' that this list is not complete. And the work in progress on the JCR 2.0 ([http://jcp.org/en/jsr/detail?id=283 JSR-283]) implementation in Jackrabbit creates more of these points and two specifications to "diff" against. If you have any questions on this topic, the best place to ask are the [http://jackrabbit.apache.org/mailing-lists.html jackrabbit mailing lists] (start on the users list).

== Additional Features ==
 * XPath element() function also allows for mixin node types in the second argument (not only primary node types as mandated by the spec in section 6.6.4.13 "element() Node Test")

== Implementation Choice ==
 * Changes made by different sessions: Jackrabbit employs a copy-on-write model, ie. any non-modified item in one session will always reflect the persisted state of that item (section 7.1.3.4 "Seeing Changes Made by Other Sessions").