You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jackrabbit.apache.org by tr...@apache.org on 2015/04/02 09:13:58 UTC

svn commit: r1670829 [3/7] - in /jackrabbit/site/trunk: ./ attic/ attic/cgi-bin/ attic/content/ attic/lib/ attic/templates/ cgi-bin/ content/ lib/ src/ src/site/ src/site/markdown/ src/site/resources/ src/site/resources/css/ src/site/resources/images/ ...

Added: jackrabbit/site/trunk/src/site/markdown/how-to-map-associations-between-objects.md
URL: http://svn.apache.org/viewvc/jackrabbit/site/trunk/src/site/markdown/how-to-map-associations-between-objects.md?rev=1670829&view=auto
==============================================================================
--- jackrabbit/site/trunk/src/site/markdown/how-to-map-associations-between-objects.md (added)
+++ jackrabbit/site/trunk/src/site/markdown/how-to-map-associations-between-objects.md Thu Apr  2 07:13:56 2015
@@ -0,0 +1,130 @@
+Title: How to map associations between objects
+<a name="Howtomapassociationsbetweenobjects-Overview"></a>
+## Overview
+
+This tutorial explains how to map associations between objects (1:1 and
+1:n). You can find the tutorial code sample from [here](^beans_and_collections.zip.html)
+. It is based on Maven and ready to be used inside Eclipse. If you have
+some configuration issues, please review the tutorial "[A simple OCM
+project with Maven & Eclipse]". 
+
+<a name="Howtomapassociationsbetweenobjects-TheContentModel"></a>
+## The Content Model 
+
+We will extend the content model created in the previous tutorial [5' with Jackrabbit OCM](5'-with-jackrabbit-ocm.html)
+. Each PressRelease is made by an Author and it is possible to add some
+references (URL). 
+
+So, we have to add 2 new associations in our model  : 
+- An 1:1 association between a PressRelease and an Author.
+- An 1:n association between PresseRelease and Url. 
+
+
+Here is the main java class, the PressRelease : 
+
+
+    @Node
+    public class PressRelease
+    {
+        @Field(path=true) private String path;
+        @Field  private String title;
+        @Field  private Date pubDate;
+        @Field  private String content;
+        @Bean private Author author;
+        @Collection  List<Url> urls;
+        
+        //if you want a map instead of a list, use the following declaration
+        @Collection Map<String,Url> map;
+        
+     [... Add here getters & setters ...]
+    
+    }
+
+
+Since the tutorial [5' with Jackrabbit OCM](5'-with-jackrabbit-ocm.html)
+, we can understand the goal of the annotations @Node and @Field. 
+An association 1:1 can be specified with the annotation @Bean like 
+
+    @Bean private Author author;
+
+
+It is possible to set extra settings with this annotation but it is out of
+the scope of this tutorial.You can review the code of the Author class
+which is very simple. As you will see, it is not mandatory to add
+annotation @Field(path=true) in the Author class because it is an
+aggregation of a PressRelease.
+
+An 1:n association can be specified with the annotation @Collection like 
+
+    @Collection  List<Url> urls;
+
+
+For this kind of association, you can also use a Map instead of a
+Collection
+
+    @Collection Map<String,Url> map;
+
+
+
+Right now, the support of Map is limited to the usage of String for the key
+because the map key will be used as the Node name.
+
+
+<a name="Howtomapassociationsbetweenobjects-Howarethoseobjectsstoredintherepository?"></a>
+## How are those objects stored in the repository ?
+
+
+For this tutorial each java class is mapped into the "nt:unstructured" node
+type. Making this kind of mapping is quite flexible because it does not
+imply specific repository configuration. There is no constraints in the JCR
+repository. All constrains are defined in the java code. 
+
+{info}
+Note : It is possible to associate a specific node type to each java class
+but this imply more repository configurations. 
+       It is also possible to change the corresponding JCR node structure
+by using specific Bean or Collection converters. 
+       Later, we will add more tutorials on OCM converters. 
+{info}
+
+Following our example, the Author and Urls nodes will be created as
+subnodes of a press release. 
+Here is an example of the correspoding JCR structure : 
+
+
+    - PressRelease_1 
+    	* path : "/mypath/myrelease"
+    	* title : "..."
+    	* pubDate : 10/06/08
+    	* content :  "...."
+    	- Author
+    		* firstName : "..."
+    		* lastName : "..."
+    	- urls
+    		* url1 
+    			* url : "http://...."
+    			* caption : "..."
+    			* description : "..."
+    		* url2 
+    			* url : "http://...."
+    			* caption : "..."
+    			* description : "..."
+    		...
+    	- map
+    	   * Apache
+    	       * url : "http://www.apache.org"
+    	       * caption : "..."
+    	       * description : "..."
+                
+    	   * Jackrabbit
+    	      * url : "http://jackrabbit.apache.org"
+    	      * caption : "..."
+    	      * description : "..."
+    		
+
+
+<a name="Howtomapassociationsbetweenobjects-Downloadthetutorialcode"></a>
+## Download the tutorial code
+
+You can download the OCM project from [here](^beans_and_collections.zip.html)
+

Added: jackrabbit/site/trunk/src/site/markdown/index-readers.md
URL: http://svn.apache.org/viewvc/jackrabbit/site/trunk/src/site/markdown/index-readers.md?rev=1670829&view=auto
==============================================================================
--- jackrabbit/site/trunk/src/site/markdown/index-readers.md (added)
+++ jackrabbit/site/trunk/src/site/markdown/index-readers.md Thu Apr  2 07:13:56 2015
@@ -0,0 +1,109 @@
+Title: Index readers
+Jackrabbit uses Lucene as the underlying index implementation and provides
+several extensions and customizations that help improve performance in an
+environment where changes to the index are frequent. The extensions also
+cover features that are not supported by Lucene, like hierarchical queries.
+
+{center}!index-readers-per-segment.jpg!{center}
+
+<a name="Indexreaders-CachingIndexReader"></a>
+## CachingIndexReader
+
+The CachingIndexReader is at the very bottom of the index reader stack in
+Jackrabbit. It's main purpose is to cache the parent relationship of a
+node. Each node is represented with a document in the index and one of the
+fields is _:PARENT. The value of this field is the string representation of
+the parent nodes UUID. In case of the root node the the parent field
+contains an empty string as its value. Several queries in Jackrabbit are
+hierarchical and check whether a node is a descendant of another node. For
+the very simple case, where one needs to know if a node is the child of
+another node, we can just look up both nodes (lucene documents) in the
+index and compare the parent field on one node with the _:UUID field of the
+other. If they match the one is the child of the other node. When it comes
+to evaluating a descendant axis, this becomes much more expensive and will
+cause lots of document lookups in lucene. By caching the parent child
+relationship of documents, hierarchical operations can be executed much
+faster.
+
+The cache consists of an array of DocId instances. The length of this array
+corresponds to the number of documents accessible through the index reader.
+That is every document in the index has a corresponding cache entry in the
+array. Initially the cache is empty and is filled as it is accessed. There
+are two kinds of DocIds: PlainDocId and UUIDDocId. When the parent of a
+node resides in the same index segment a PlainDocId is created, which
+simply contains the document number of the parent. If the parent resides in
+a different index segment a UUIDDocId is created, which contains the UUID
+of the parent node. When a UUIDDocId is resolved it is passed an index
+reader, which allows it to get the document number for the UUID and cache
+it for later reuse.
+
+<a name="Indexreaders-OverwritingDocId"></a>
+## Overwriting DocId
+
+It may happen that a PlainDocId is present in the cache of a
+CachingIndexReader but must be considered invalid in the context of a call.
+CachingIndexReader.getParent() may be called from a ReadOnlyIndexReader
+instance which has the target of the PlainDocId in the set of deleted
+document. This indicates that the nodes has been deleted or modified. Thus
+it has traveled to another index segment. In this case the PlainDocId is
+overwritten with a UUIDDocId. The opposite never happens. A UUIDDocId is
+never overwritten with a PlainDocId because when a document is added to an
+index a new CachingIndexReader is created.
+
+<a name="Indexreaders-SharedIndexReader"></a>
+## SharedIndexReader
+
+The SharedIndexReader wraps a CachingIndexReader and adds a reference count
+facility. A SharedIndexReader is kept open for the entire lifetime of a
+PersistentIndex. Even if documents are marked deleted in the underlying
+index (by another thread through CommittableIndexReader), the
+SharedIndexReader will still be kept open and considers the documents as
+valid. The reference counting is needed because it may happen that a client
+of the SharedIndexReader is still in use while the underlying
+PersistentIndex is closed. This may happen when the index merger replaces
+indexes while a query still operates on the indexes to be deleted. Using
+reference counts, closing the SharedIndexReader is delayed until all
+clients are finished with the  SharedIndexReader.
+
+<a name="Indexreaders-ReadOnlyIndexReader"></a>
+## ReadOnlyIndexReader
+
+The inconsistency introduced by the SharedIndexReader (considers deleted
+documents as still valid) is corrected by the ReadOnlyIndexReader. Whenever
+a new instance of this reader is created it copies the currently marked
+deleted documents from the CommittableIndexReader. At the same time all
+methods that attempt delete documents will throw a
+UnsupportedOperationException.
+
+<a name="Indexreaders-CommittableIndexReader"></a>
+## CommittableIndexReader
+
+This is the index reader where documents are marked deleted in a
+PersistentIndex. As with the SharedIndexReader the CommittableIndexReader
+is kept open for the entire lifetime of the PersistentIndex. To achieve
+this the CommittableIndexReader exposes a method commitDeleted, which
+forces the underlying native lucene index reader to commit changes. Only
+committing changes whithout closing the index reader is otherwise not
+possible using the plain lucene index reader.
+
+<a name="Indexreaders-Combiningtheindexsegments"></a>
+## Combining the index segments
+
+{center}!index-readers-per-query-handler.jpg!{center}
+
+<a name="Indexreaders-CachingMultiIndexReader"></a>
+## CachingMultiIndexReader
+
+The index for the content of a workspace consists of multiple segments,
+that is multiple ReadOnlyIndexReaders. They are combined in a MultiIndex
+using a CachingMultiIndexReader. In order to speed up lookups by UUID the
+CachingMultiIndexReader also has a DocNumberCache. This cache uses a LRU
+algorithm to keep a limitted amount of UUID to document number mappings.
+
+<a name="Indexreaders-CombinedIndexReader"></a>
+## CombinedIndexReader
+
+This index reader is similar to the CachingMultiIndexReader, in fact both
+implement MultiIndexReader and HierarchyResolver. A CombinedIndexReader is
+created when a query needs an index reader that spans both the workspace
+index as well as the jcr:system index, where the version store resides.

Added: jackrabbit/site/trunk/src/site/markdown/index.md
URL: http://svn.apache.org/viewvc/jackrabbit/site/trunk/src/site/markdown/index.md?rev=1670829&view=auto
==============================================================================
--- jackrabbit/site/trunk/src/site/markdown/index.md (added)
+++ jackrabbit/site/trunk/src/site/markdown/index.md Thu Apr  2 07:13:56 2015
@@ -0,0 +1,166 @@
+<!--
+   Licensed to the Apache Software Foundation (ASF) under one or more
+   contributor license agreements.  See the NOTICE file distributed with
+   this work for additional information regarding copyright ownership.
+   The ASF licenses this file to You under the Apache License, Version 2.0
+   (the "License"); you may not use this file except in compliance with
+   the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.
+-->
+
+Welcome to Apache Jackrabbit
+============================
+
+The Apache Jackrabbit™ content repository is a fully conforming implementation 
+of the Content Repository for Java Technology API (JCR, specified in 
+[JSR 170](http://jcp.org/en/jsr/detail?id=170) and [JSR 283](http://jcp.org/en/jsr/detail?id=283)).
+
+A content repository is a hierarchical content store with support for
+structured and unstructured content, full text search, versioning,
+transactions, observation, and more.
+
+Apache Jackrabbit is a project of the [Apache Software Foundation](http://www.apache.org/)
+
+## Apache Jackrabbit News
+
+#### March 26th, 2015: Apache Jackrabbit 2.10.0 released
+Apache Jackrabbit 2.10 is an incremental feature release based on and compatible with earlier stable Jackrabbit 2.x releases. 
+See the downloads page for more details.
+
+#### March 10th, 2015: Apache Jackrabbit Oak 1.0.12 released
+Jackrabbit Oak 1.0.12 is a patch release that contains fixes and improvements over the previous 1.0.11 release. 
+See the downloads page for more details.
+
+#### March 9th, 2015: Apache Jackrabbit Oak 1.1.7 released
+Jackrabbit Oak 1.1.7 is an unstable release cut directly from trunk, with a focus on new features and other improvements. 
+See the downloads page for more details.
+
+#### February 25th, 2015: Apache Jackrabbit FileVault 3.1.16 released
+Jackrabbit FileVault 3.1.16 is current stable release of the recently donated repository content synchronization tool. 
+See the downloads page for more details.
+
+#### February 9th, 2015: Apache Jackrabbit Oak 1.1.6 released
+Jackrabbit Oak 1.1.6 is an unstable release cut directly from trunk, with a focus on new features and other improvements. 
+See the downloads page for more details.
+
+#### February 6th, 2015: Apache Jackrabbit 2.9.1 released
+Apache Jackrabbit 2.9.x is an unstable series of releases cut directly from Jackrabbit trunk, with a focus on new features 
+and other improvements. See the downloads page for more details.
+
+#### February 3rd, 2015: Apache Jackrabbit Oak 1.0.11 released
+Jackrabbit Oak 1.0.11 is a patch release that contains fixes and improvements over the previous 1.0.10 release.
+
+#### February 2nd, 2015: Apache Jackrabbit Oak 1.0.10 released
+Jackrabbit Oak 1.0.10 is a patch release that contains fixes and improvements over the previous 1.0.9 release.
+
+#### January 23rd, 2015: Apache Jackrabbit Oak 1.1.5 released
+Jackrabbit Oak 1.1.5 is an unstable release cut directly from trunk, with a focus on new features and other improvements. 
+See the downloads page for more details.
+
+#### January 13th, 2015: Apache Jackrabbit Oak 1.1.4 released
+Jackrabbit Oak 1.1.4 is an unstable release cut directly from trunk, with a focus on new features and other improvements.
+
+## News in 2014
+
+#### December 22nd, 2014: Apache Jackrabbit Oak 1.0.9 released
+Jackrabbit Oak 1.0.9 is a patch release that contains fixes and improvements over the previous 1.0.8 release.
+
+#### December 15th, 2014: Apache Jackrabbit Oak 1.1.3 released
+Jackrabbit Oak 1.1.3 is an unstable release cut directly from trunk, with a focus on new features and other improvements.
+
+#### December 19th, 2014: Apache Jackrabbit FileVault 3.1.14 released
+Jackrabbit FileVault 3.1.14 is current stable release of the recently donated repository content synchronization tool. 
+See the downloads page for more details.
+
+#### November 10th, 2014: Apache Jackrabbit Oak 1.1.2 released
+Jackrabbit Oak 1.1.2 is an unstable release cut directly from trunk, with a focus on new features and other improvements.
+
+#### November 4th, 2014: Apache Jackrabbit Oak 1.0.8 released
+Jackrabbit Oak 1.0.8 is a patch release that contains fixes and improvements over the previous 1.0.7 release.
+
+#### October 27th, 2014: Apache Jackrabbit FileVault 3.1.8 released
+Jackrabbit FileVault 3.1.8 is current stable release of the recently donated repository content synchronization tool.
+
+#### October 17th, 2014: Apache Jackrabbit Oak 1.1.1 released
+Jackrabbit Oak 1.1.1 is an unstable release cut directly from trunk, with a focus on new features and other improvements.
+
+#### October 14th, 2014: Apache Jackrabbit Oak 1.0.7 released
+Jackrabbit Oak 1.0.7 is a patch release that contains fixes and improvements over the previous 1.0.6 release.
+
+#### October 6th, 2014: Apache Jackrabbit Oak 1.1.0 released
+Jackrabbit Oak 1.1.0 is an unstable release cut directly from trunk, with a focus on new features and other improvements.
+
+#### September 25th, 2014: Apache Jackrabbit Oak 1.0.6 released
+Jackrabbit Oak 1.0.6 is a patch release that contains fixes and improvements over the previous 1.0.5 release.
+
+#### August 29th, 2014: Apache Jackrabbit Oak 1.0.5 released
+Jackrabbit Oak 1.0.5 is a patch release that contains fixes and improvements over the previous 1.0.4 release.
+
+#### August 28th, 2014: Apache Jackrabbit 2.9.0 released
+Apache Jackrabbit 2.9.x is an unstable series of releases cut directly from Jackrabbit trunk, with a focus on new features 
+and other improvements.
+
+#### August 4th, 2014: Apache Jackrabbit Oak 1.0.4 released
+Jackrabbit Oak 1.0.4 is a patch release that contains fixes and improvements over the previous 1.0.3 release.
+
+#### July 28th, 2014: Apache Jackrabbit Oak 1.0.3 released
+Jackrabbit Oak 1.0.3 is a patch release that contains fixes and improvements over the previous 1.0.2 release.
+
+#### July 22nd, 2014: Apache Jackrabbit Oak 1.0.2 released
+Jackrabbit Oak 1.0.2 is a patch release that contains fixes and improvements over the previous 1.0.1 release.
+
+#### June 26th, 2014: Apache Jackrabbit Oak 1.0.1 released
+Jackrabbit Oak 1.0.1 is a patch release that contains fixes and improvements over the previous 1.0.0 release.
+
+#### May 12th, 2014: Apache Jackrabbit 2.8.0 released
+Apache Jackrabbit 2.8 is an incremental feature release based on and compatible with earlier stable Jackrabbit 2.x releases. 
+See the downloads page for more details.
+
+#### April 25th, 2014: Apache Jackrabbit FileVault 3.1.6 released
+Jackrabbit FileVault 3.1.6 is current stable release of the recently donated repository content synchronization tool.
+
+#### April 8th, 2014: Apache Jackrabbit Oak 0.20.0 released
+Jackrabbit Oak 0.20.0 is to be considered alpha-level software. Use at your own risk with no stability or compatibility guarantees.
+
+#### April 5th, 2014: Apache Jackrabbit FileVault 3.1.2 released
+Jackrabbit FileVault 3.1.2 is current stable release of the recently donated repository content synchronization tool.
+
+#### March 31th, 2014: Apache Jackrabbit FileVault 3.1.0 released
+Jackrabbit FileVault 3.1.0 is the second release of the recently donated repository content synchronization tool.
+
+#### March 24th, 2014: Apache Jackrabbit Oak 0.19 released
+Jackrabbit Oak 0.19 is to be considered alpha-level software. Use at your own risk with no stability or compatibility guarantees.
+
+#### March 17th, 2014: Apache Jackrabbit 2.7.5 released
+Apache Jackrabbit 2.7.x is an unstable series of releases cut directly from Jackrabbit trunk, with a focus on new features 
+and other improvements.
+
+#### March 11th, 2014: Apache Jackrabbit Oak 0.18 released
+Jackrabbit Oak 0.18 is to be considered alpha-level software. Use at your own risk with no stability or compatibility guarantees.
+
+#### February 26th, 2014: Apache Jackrabbit Oak 0.17.1 released
+Jackrabbit Oak 0.17.1 is to be considered alpha-level software. Use at your own risk with no stability or compatibility guarantees.
+
+#### February 11th, 2014: Apache Jackrabbit 2.7.4 released
+Apache Jackrabbit 2.7.x is an unstable series of releases cut directly from Jackrabbit trunk, with a focus on new features 
+and other improvements.
+
+#### February 10th, 2014: Apache Jackrabbit Oak 0.16 released
+Jackrabbit Oak 0.16 is to be considered alpha-level software. Use at your own risk with no stability or compatibility guarantees.
+
+#### January 27th, 2014: Apache Jackrabbit Oak 0.15 released
+Jackrabbit Oak 0.15 is to be considered alpha-level software. Use at your own risk with no stability or compatibility guarantees.
+
+#### January 13th, 2014: Apache Jackrabbit Oak 0.14 released
+Jackrabbit Oak 0.14 is to be considered alpha-level software. Use at your own risk with no stability or compatibility guarantees.
+
+## Older News
+
+See the [news archive](news-archive.html) for past news.
\ No newline at end of file

Added: jackrabbit/site/trunk/src/site/markdown/issue-tracker.md
URL: http://svn.apache.org/viewvc/jackrabbit/site/trunk/src/site/markdown/issue-tracker.md?rev=1670829&view=auto
==============================================================================
--- jackrabbit/site/trunk/src/site/markdown/issue-tracker.md (added)
+++ jackrabbit/site/trunk/src/site/markdown/issue-tracker.md Thu Apr  2 07:13:56 2015
@@ -0,0 +1,95 @@
+Title: Issue Tracker
+Apache Jackrabbit uses Jira for tracking bug reports and requests for
+improvements, new features, and other changes.
+
+The issue tracker is available at https://issues.apache.org/jira/browse/JCR
+and is readable by everyone. A Jira account is needed to create new issues
+and to comment on existing issues. Use the [registration form](https://issues.apache.org/jira/secure/Signup!default.jspa)
+ to request an account if you do not already have one.
+
+<a name="IssueTracker-Issueworkflow"></a>
+## Issue workflow
+
+When an issue is created, it's in the *Open* state. This is the time for
+describing the issue and discussing possible ways of solving it. If a
+proposed patch is attached, then the issue can optionally be moved to the
+*Patch available* state to give it more visibility. If the patch is
+cancelled because more work is needed, the issue moves back to the *Open*
+state.
+
+Once the issue is solved, the committer who committed the changes marks the
+issue as *Resolved* with resolution type _Fixed_. Other resolution types
+like _Duplicate_, _Invalid_ or _Won't Fix_ are used when resolving issues
+that for one reason or another require no changes in the codebase. An issue
+can be *Reopened* if the committed fix is found to be not good enough.
+
+When an issue is resolved as fixed, the committer should set the "Fix
+Version(s)" field to the next trunk version to mark that the change will be
+included in that release. If the fix is also backported to one or more of
+the maintenance branches (for backporting, use "svn merge -c _revision_
+^/jackrabbit/trunk" in the root of the branch) the version numbers of the
+relevant next maintenance releases should also be included in the "Fix
+Version(s)" field.
+
+Finally, once a release containing the change has been made, the release
+manager will mark the issue *Closed*, after which the issue can no longer
+be reopened (since the release can obviously no longer be changed).
+Potential regressions or other related problems should be tracked in
+separate followup issues.
+
+<a name="IssueTracker-Issuecontents"></a>
+## Issue contents
+
+See below for guidelines on how to use the various fields in an issue.
+
+<a name="IssueTracker-Issuetype"></a>
+### Issue type
+
+When creating a new issue, select the issue type based as follows:
+
+     <table>
+     <tr><th> Issue type	  </th><th> Description </th></tr>
+     <tr><td>  *Bug*	  </td><td>  Bug reports are used for cases where Jackrabbit fails
+     not function as it should (as defined by the JCR specification or some
+     other documentation). If you are not certain whether the issue you've found
+     is actually a bug, please ask the Jackrabbit [mailing lists](mailing-lists.html)
+      first for help. </td></tr>
+     <tr><td>  *New Feature*  </td><td>  Use a feature request when Jackrabbit does not have
+     some functionality you need. </td></tr>
+     <tr><td>  *Improvement*  </td><td>  Use an improvement request to suggest improvements to
+     existing features. Typical improvement requests are about updating
+     documentation, increasing stability and performance, simplifying the
+     implementation, or other such changes that make Jackrabbit better without
+     introducing new features or fixing existing bugs. </td></tr>
+     <tr><td>  *Test*	  </td><td>  Use this type when contributing test cases for
+     existing features. Normally test cases should be contributed as a part of
+     the original feature request or as regression tests associated with bug
+     reports, but sometimes you just want to extend test coverage by introducing
+     new test cases. This issue type is for such cases. </td></tr>
+     <tr><td>  *Task*	  </td><td>  Used only for issues related to project
+     infrastructure. </td></tr>
+     </table>
+
+<a name="IssueTracker-Issuesummary,environmentanddescription"></a>
+### Issue summary, environment and description
+
+The issue summary should be a short and clear statement that indicates the
+scope of the issue. You are probably being too verbose if you exceed the
+length of the text field. Use the Environment and Description fields to
+provide more detailed information.
+
+<a name="IssueTracker-Issuepriority"></a>
+### Issue priority
+
+Issue priority should be set according to the following:
+
+     <table>
+     <tr><th> Issue priority </th><th> Description </td></tr>
+     <tr><td>  *Blocker*	  </td><td>  Legal or other fundamental issue that makes it
+     impossible to release Jackrabbit code </td></tr>
+     <tr><td>  *Critical*	  </td><td>  Major loss of functionality that affects many
+     Jackrabbit users </td></tr>
+     <tr><td>  *Major*	  </td><td>  Important issue that should be resolved soon </td></tr>
+     <tr><td>  *Minor*	  </td><td>  Nice to have issues </td></tr>
+     <tr><td>  *Trivial*	  </td><td>  Trivial changes that can be applied whenever someone
+     has extra time </td></tr>

Added: jackrabbit/site/trunk/src/site/markdown/jackrabbit-api.md
URL: http://svn.apache.org/viewvc/jackrabbit/site/trunk/src/site/markdown/jackrabbit-api.md?rev=1670829&view=auto
==============================================================================
--- jackrabbit/site/trunk/src/site/markdown/jackrabbit-api.md (added)
+++ jackrabbit/site/trunk/src/site/markdown/jackrabbit-api.md Thu Apr  2 07:13:56 2015
@@ -0,0 +1,15 @@
+Title: Jackrabbit API
+This is the API component of the Apache Jackrabbit project. This component
+contains the interface extensions that Apache Jackrabbit supports in
+addition to the standard JCR API. You can use these interfaces to access
+Jackrabbit-specific functionality.
+
+<a name="JackrabbitAPI-APIdocumentation"></a>
+## API documentation
+
+* [jackrabbit-api 1.4](http://jackrabbit.apache.org/api/1.4/org/apache/jackrabbit/api/package-summary.html)
+
+<a name="JackrabbitAPI-ExternalDependencies"></a>
+## External Dependencies
+
+* [JCR](jcr.html)

Added: jackrabbit/site/trunk/src/site/markdown/jackrabbit-architecture.md
URL: http://svn.apache.org/viewvc/jackrabbit/site/trunk/src/site/markdown/jackrabbit-architecture.md?rev=1670829&view=auto
==============================================================================
--- jackrabbit/site/trunk/src/site/markdown/jackrabbit-architecture.md (added)
+++ jackrabbit/site/trunk/src/site/markdown/jackrabbit-architecture.md Thu Apr  2 07:13:56 2015
@@ -0,0 +1,104 @@
+Title: Jackrabbit Architecture
+* [How Jackrabbit works](how-jackrabbit-works.html)
+* [Repository lifecycle](repository-lifecycle.html)
+* [Search implementation](search-implementation.html)
+* [Index readers](index-readers.html)
+* [Concurrency control](concurrency-control.html)
+
+The general architecture of Jackrabbit can be described in three Layers: A
+Content Application Layer, an API Layer and a Content Repository
+Implementation Layer.
+
+!overview.png!
+
+<a name="JackrabbitArchitecture-ContentApplications"></a>
+## Content Applications
+
+Content Applications interact through the JSR-170 API with the Content
+Repository Implementation. There are numerous applications that are
+available for JSR-170 repositories, some of them are very generic (like a
+WebDAV server) other applications can be very specific and make use of the
+content repository as a store for the information that is used by the
+applications. Java Applications can use a JSR-170 content repository as a
+replacement for anything from property-files, XML-configuration, certain
+portions of relational database functionality to straight file system or
+blob-management. Using a content repository allows an application to deal
+with an arbitrarily large hierarchical space in a scalable manner
+automatically profiting from the repository services such as versioning,
+query, transactions or namespaces which make a content repository an ideal
+data store for many applications.
+
+A "Generic Content Application" (an application that has no particular
+functional focus but just allows for generic introspection and manipulation
+of the repository) uses the capabilities of the node types, access control
+and other facilities to display a user interface or a network protocol to
+the end user, seemingly independent from the content that is stored in the
+repository. Examples of such generic applications are "The Content
+Explorer", "WebDAV Server" or a "Subversion Server". (Or generic Portal,
+CMS or DMS applications).
+
+A "Specialized Content Application" operates under the assumption that
+there are certain node types that it operates on, and that it is familiar
+at least partially with the data model exposed by defined node types.
+Mostly these node types are defined by the application itself and ship with
+the application. These applications use a content repository as their
+persistence layer as a natural evolution from the use of an RDBMS or a file
+system. Examples of "Specialized Content Applications" have a very wide
+range from a "DVD Collection Management", to a "Message Board", to
+"Workflow and BPM" but also possibly complete next generation "Enterprise
+Resource Planning Systems".
+
+<a name="JackrabbitArchitecture-ContentRepositoryAPI"></a>
+## Content Repository API
+
+The Content Repository API Layer is split into two major sections.
+
+* The Content Repository API defined by JSR-170
+* A number features of a content repository, that have been removed from
+the JSR-170 specification since they are difficult to implement on existing
+non-java-based content repositories and administrational Repository tasks
+that have also been deliberately excluded from JSR-170
+
+There are only very few (mostly administrational) applications which make
+use of the non-JSR-170 APIs provided by Jackrabbit.
+
+The boxes in the architecture chart do not symbolize package names or class
+names directly but mostly semantically grouped blocks of functionality.
+
+<a name="JackrabbitArchitecture-ContentRepositoryImplementation"></a>
+## Content Repository Implementation
+
+The content Repository Implementation portion of the architecture chart
+reflects the major building blocks of the jackrabbit content repository
+implementation.
+
+The size of the blocks symbolizes roughly the amount of code and therefore
+the complexity of the individual functional block. Again the functional
+blocks do not directly map to package or class names.
+
+There are three scopes in a content repository: A repository scope, a
+workspace scope and a session scope.
+
+Every function that is operated against a repository can be attributed to
+at least one of these scopes, some functions can operate on more than one
+scope.
+
+* Repository
+* Nodetype
+* Version
+* NamespaceRegistry
+* Workspace
+* Query
+* Observation
+* State
+* Xml
+* Session
+* Path
+* HierarchyManager
+* QName
+* ItemImpl, PropertyImpl, NodeImpl
+* ItemId, PropertyId, NodeId
+* ItemManager
+
+This is not a complete list but includes some of the most important
+component of the content repository implementation.

Added: jackrabbit/site/trunk/src/site/markdown/jackrabbit-chair-2006-resolution.md
URL: http://svn.apache.org/viewvc/jackrabbit/site/trunk/src/site/markdown/jackrabbit-chair-2006-resolution.md?rev=1670829&view=auto
==============================================================================
--- jackrabbit/site/trunk/src/site/markdown/jackrabbit-chair-2006-resolution.md (added)
+++ jackrabbit/site/trunk/src/site/markdown/jackrabbit-chair-2006-resolution.md Thu Apr  2 07:13:56 2015
@@ -0,0 +1,31 @@
+Title: Jackrabbit Chair 2006 Resolution
+_From the [minutes](http://www.apache.org/foundation/records/minutes/2006/board_minutes_2006_08_16.txt)
+ of the Apache board meeting on August 16th, 2006:_
+
+
+     6. Special Orders
+    
+        A. Resolution to change the Chair of the Jackrabbit PMC
+    
+           WHEREAS, the Board of Directors heretofore appointed Roy
+           T. Fielding to the office of Vice President, Apache Jackrabbit,
+           and
+    
+           WHEREAS, the Board of Directors is in receipt of the
+           resignation of Roy T. Fielding from the office of Vice
+           President, Apache Jackrabbit;
+    
+           NOW, THEREFORE, BE IT RESOLVED, that Roy T. Fielding is
+           relieved and discharged from the duties and responsibilities of
+           the office of Vice President, Apache Jackrabbit, and
+    
+           BE IT FURTHER RESOLVED, that Jukka Zitting be and hereby is
+           appointed to the office of Vice President, Apache Jackrabbit,
+           to serve in accordance with and subject to the direction of the
+           Board of Directors and the Bylaws of the Foundation until
+           death, resignation, retirement, removal or disqualification, or
+           until a successor is appointed.
+    
+          Special Order 6A, Change the Chair of the Jackrabbit PMC, was
+          approved by Unanimous Vote.
+

Added: jackrabbit/site/trunk/src/site/markdown/jackrabbit-components.md
URL: http://svn.apache.org/viewvc/jackrabbit/site/trunk/src/site/markdown/jackrabbit-components.md?rev=1670829&view=auto
==============================================================================
--- jackrabbit/site/trunk/src/site/markdown/jackrabbit-components.md (added)
+++ jackrabbit/site/trunk/src/site/markdown/jackrabbit-components.md Thu Apr  2 07:13:56 2015
@@ -0,0 +1,35 @@
+Title: Jackrabbit Components
+The Apache Jackrabbit project consists of a number of related components.
+The main components are:
+
+* [Jackrabbit API](jackrabbit-api.html)
+* [Jackrabbit JCR Commons](jackrabbit-jcr-commons.html)
+* [Jackrabbit JCR Tests](jackrabbit-jcr-tests.html)
+* [Jackrabbit Core](jackrabbit-core.html)
+* [Jackrabbit Text Extractors](jackrabbit-text-extractors.html)
+ (replaced by [Tika|http://lucene.apache.org/tika/]
+ in Jackrabbit 2.x)
+* [Jackrabbit JCR-RMI](jackrabbit-jcr-rmi.html)
+* [Jackrabbit WebDAV Library](jackrabbit-webdav-library.html)
+* [Jackrabbit JCR Client](jackrabbit-jcr-client.html)
+* [Jackrabbit JCR to DAV](jackrabbit-jcr-to-dav.html)
+* [Jackrabbit JCR Server](jackrabbit-jcr-server.html)
+* [Jackrabbit JCR Servlet](jackrabbit-jcr-servlet.html)
+* [Jackrabbit Web Application](jackrabbit-web-application.html)
+* [Jackrabbit JCA Resource Adapter](jackrabbit-jca-resource-adapter.html)
+* [Jackrabbit SPI](jackrabbit-spi.html)
+* [Jackrabbit SPI Commons](jackrabbit-spi-commons.html)
+* [Jackrabbit JCR to SPI](jackrabbit-jcr-to-spi.html)
+* [Jackrabbit SPI to JCR](jackrabbit-spi-to-jcr.html)
+* [Jackrabbit SPI to DAV](jackrabbit-spi-to-dav.html)
+* [Jackrabbit Standalone Server](standalone-server.html)
+* [Jackrabbit OCM](jackrabbit-ocm.html)
+ ([Jackrabbit commons|http://jackrabbit.apache.org/commons/] component
+since Jackrabbit 1.6)
+* [Jackrabbit OCM Node Management](jackrabbit-ocm-node-management.html)
+ ([Jackrabbit commons|http://jackrabbit.apache.org/commons/] component
+since Jackrabbit 1.6)
+
+In addition there are a number of contributed components in the *sandbox*
+folder of the Jackrabbit project. These components are not yet considered
+stable enough to be included in the official Apache Jackrabbit releases.

Added: jackrabbit/site/trunk/src/site/markdown/jackrabbit-configuration.md
URL: http://svn.apache.org/viewvc/jackrabbit/site/trunk/src/site/markdown/jackrabbit-configuration.md?rev=1670829&view=auto
==============================================================================
--- jackrabbit/site/trunk/src/site/markdown/jackrabbit-configuration.md (added)
+++ jackrabbit/site/trunk/src/site/markdown/jackrabbit-configuration.md Thu Apr  2 07:13:56 2015
@@ -0,0 +1,372 @@
+Title: Jackrabbit Configuration
+{toc:minLevel=2}
+
+Apache Jackrabbit needs two pieces of information to set up a runtime
+content repository instance:
+
+* *Repository home directory* The filesystem path of the directory
+containing the content repository accessed by the runtime instance of
+Jackrabbit. This directory usually contains all the repository content,
+search indexes, internal configuration, and other persistent information
+managed within the content repository. Note that this is not absolutely
+required and some persistence managers and other Jackrabbit components may
+well be configured to access files and even other resources (like remote
+databases) outside the repository home directory. A designated repository
+home directory is however always needed even if some components choose to
+not use it. Jackrabbit will automatically fill in the repository home
+directory with all the required files and subdirectories when the
+repository is first instantiated.
+
+* *Repository configuration file* The filesystem path of the repository
+configuration XML file. This file specifies the class names and properties
+of the various Jackrabbit components used to manage and access the content
+repository. Jackrabbit parses this configuration file and instantiates the
+specified components when the runtime content repository instance is
+created.
+
+These two configuration parameters are passed either directly to Jackrabbit
+when creating a repository instance or indirectly through settings for a
+JNDI object factory or some other component management system.
+
+For each workspace that was created, there will also be a workspace.xml
+file created inside the workspace home directory that will be used for the
+workspace - these files have to be changed, too, because the
+workspace-specific configuration inside repository.xml is only used as a
+template for new workspaces, ie. if you use the *createWorkspace()*
+method of the Jackrabbit API, the workspace.xml is just a copy of the [Workspace](#workspace-configuration.html)
+ element inside repository.xml. You can also manually create the workspace
+folder with a workspace.xml file to create a new workspace yourself (Please
+note that depending on the [persistence manager|#Persistence configuration]
+ you will also have to setup a database and configure the access to it).
+
+<a name="JackrabbitConfiguration-Repositoryconfiguration"></a>
+## Repository configuration
+
+The repository configuration file, typically called *repository.xml*,
+specifies global options like security, versioning and clustering settings.
+A default workspace configuration template is also included in the
+repository configuration file. The exact format of this XML configuration
+file is defined in the following document type definition (DTD) files
+published by the Apache Jackrabbit project.
+
+   * [-//The Apache Software Foundation//DTD Jackrabbit 1.5//EN](http://jackrabbit.apache.org/dtd/repository-1.5.dtd)
+   * [-//The Apache Software Foundation//DTD Jackrabbit 1.4//EN](http://jackrabbit.apache.org/dtd/repository-1.4.dtd)
+   * [-//The Apache Software Foundation//DTD Jackrabbit 1.2//EN](http://jackrabbit.apache.org/dtd/repository-1.2.dtd)
+   * [-//The Apache Software Foundation//DTD Jackrabbit 1.0//EN](http://jackrabbit.apache.org/dtd/repository-1.0.dtd)
+
+All Jackrabbit 1.x versions are fully backwards compatible, so you can use
+a recent Jackrabbit version without having to modify your existing
+repository configuration. Of course you will need to make configuration
+changes if you want to enable new features like the data store introduced
+in Jackrabbit 1.4.
+
+The top-level structure of the repository configuration file is shown
+below. The *<!DOCTYPE>* declaration is optional, but if you include it
+Jackrabbit 1.5 will use XML validation to make sure that the configuration
+file is correctly formatted.
+
+
+    <!DOCTYPE Repository
+    	  PUBLIC "-//The Apache Software Foundation//DTD Jackrabbit 1.5//EN"
+    	  "http://jackrabbit.apache.org/dtd/repository-1.5.dtd">
+    <Repository>
+      <FileSystem .../>
+      <Security .../>
+      <Workspaces .../>
+      <Workspace .../>
+      <Versioning .../>
+      <SearchIndex .../>	<!-- optional -->
+      <Cluster .../>	<!-- optional, available since 1.2 -->
+      <DataStore .../>	<!-- optional, available since 1.4 -->
+    </Repository>
+
+
+Starting with Jackrabbit 1.5, the order of the configuration elements below
+*<Repository/>* is now fixed.
+
+The repository configuration elements are:
+
+   * {{[FileSystem](#file-system-configuration.html) }}: The virtual file system used by the repository to store things like
+registered namespaces and node types.
+   * {{[Security](#security-configuration.html) }}: Authentication and authorization configuration.
+   * {{[Workspaces](#workspace-configuration.html) }}: Configuration on where and how workspaces are managed.
+   * {{[Workspace](#workspace-configuration.html) }}: Default workspace configuration template.
+   * {{[Versioning](#versioning-configuration.html) }}:  Configuration of the repository-wide version store.
+   * {{[SearchIndex](#search-configuration.html) }}: Configuration of the search index that covers the repository-wide `/jcr:system` content tree. 
+   * {{[Cluster](#cluster-configuration.html) }}: Clustering configuration.
+   * {{[DataStore](#data-store-configuration.html) }}: Data store configuration.
+
+See the Jackrabbit 1.5 [default configuration](^repository.xml.html) , for an example repository configuration file.
+
+{tip}
+It is a good idea to place the *repository.xml* file _inside_ the
+repository home directory. This keeps your repository and its configuration
+nicely contained within a single directory tree.
+{tip} 
+
+<a name="JackrabbitConfiguration-Beanconfigurationelements"></a>
+### Bean configuration elements
+
+Most of the entries in the configuration file are based on the following
+generic JavaBean configuration pattern. Such configuration specifies that
+the repository should use an instance of the specified class with the
+specified properties for the named functionality.
+
+
+    <ConfigurationElement class="fully.qualified.ClassName">
+      <param name="property1" value="...">
+      <param name="property2" value="...">
+    <ConfigurationElement>
+
+
+<a name="JackrabbitConfiguration-Configurationvariables"></a>
+### Configuration variables
+
+Jackrabbit supports configuration variables of the form _$\{name\}_. These
+variables can be used to avoid hardcoding specific options in the
+configuration files. The following variables are available in all
+Jackrabbit versions:
+
+* *$\{rep.home\}:* Repository home directory.
+* *$\{wsp.name\}:* Workspace name. Only available in workspace
+configuration.
+* *$\{wsp.home\}:* Workspace home directory. Only available in workspace
+configuration.
+
+Since Jackrabbit 1.4 (see [JCR-1304](https://issues.apache.org/jira/browse/JCR-1304)
+) it has been possible to use system properties or any application-specific
+settings as configuration variables.
+
+<a name="JackrabbitConfiguration-Securityconfiguration"></a>
+## Security configuration
+
+The security configuration element is used to specify authentication and
+authorization settings for the repository. The structure of the security
+configuration element is:
+
+
+    <Security appName="Jackrabbit">
+      <SecurityManager .../> <!-- optional, available since 1.5 -->
+      <AccessManager .../>	 <!-- mandatory until 1.4, optional since 1.5 -->
+      <LoginModule .../>	 <!-- optional -->
+    </Security>
+
+
+By default Jackrabbit uses the [Java Authentication and Authorization Service](http://java.sun.com/j2se/1.4.2/docs/guide/security/jaas/JAASRefGuide.html)
+ (JAAS) to authenticate users who try to access the repository. The
+*appName* parameter in the *<Security/>* element is used as the JAAS
+application name of the repository.
+
+If JAAS authentication is not available or (as is often the case) too
+complex to set up, Jackrabbit allows you to specify a repository-specific
+JAAS [LoginModule](http://java.sun.com/j2se/1.4.2/docs/api/javax/security/auth/spi/LoginModule.html)
+ that is then used for authenticating repository users. The default [SimpleLoginModule|http://jackrabbit.apache.org/api/1.5/org/apache/jackrabbit/core/security/SimpleLoginModule.html]
+ class included in Jackrabbit implements a trivially simple authentication
+mechanism that accepts any username and any password as valid
+authentication credentials.
+
+Once a user has been authenticated, Jackrabbit will use the configured [AccessManager](http://jackrabbit.apache.org/api/1.5/org/apache/jackrabbit/core/security/AccessManager.html)
+ to control what parts of the repository content the user is allowed to
+access and modify. The default [SimpleAccessManager|http://jackrabbit.apache.org/api/1.5/org/apache/jackrabbit/core/security/SimpleAccessManager.html]
+ class included in Jackrabbit implements a trivially simple authorization
+mechanism that grants full read access to all users and write access to
+everyone except anonymous users.
+
+The slightly more advanced [SimpleJBossAccessManager](http://jackrabbit.apache.org/api/1.5/org/apache/jackrabbit/core/security/SimpleJBossAccessManager.html)
+ class was added in Jackrabbit 1.3 (see [JCR-650|https://issues.apache.org/jira/browse/JCR-650]
+). This class is designed for use with the [JBoss Application Server|http://www.jboss.org/jbossas/]
+, where it maps JBoss roles to Jackrabbit permissions.
+
+<a name="JackrabbitConfiguration-Workspaceconfiguration"></a>
+## Workspace configuration
+
+A Jackrabbit repository contains one or more workspaces that are each
+configured in a separate *workspace.xml* configuration file. The
+*Workspaces* element of the repository configuration specifies where and
+how the workspaces are managed. The repository configuration also contains
+a default workspace configuration template that is used to create the
+*workspace.xml* file of a new workspace unless more specific
+configuration is given when the workspace is created. See the
+*createWorkspace* methods in the [JackrabbitWorkspace](http://jackrabbit.apache.org/api/1.5/org/apache/jackrabbit/api/JackrabbitWorkspace.html)
+ interface for more details on workspace creating workspaces.
+
+The workspace settings in the repository configuration file are:
+
+
+    <Workspaces rootPath="${rep.home}/workspaces"
+    	    defaultWorkspace="default"
+    	    configRootPath="..."  <!-- optional -->
+    	    maxIdleTime="..."/>   <!-- optional -->
+    
+    <Workspace .../>   <!-- default workspace configuration template -->
+
+
+The following global workspace configuration options are specified in the
+*Workspaces* element:
+
+   * *rootPath*: The native file system directory for workspaces. A
+subdirectory is automatically created for each workspace, and the path of
+that subdirectory can be used in the workspace configuration as the
+*$\{wsp.path\} *variable.
+   * *defaultWorkspace*: Name of the default workspace. This workspace is
+automatically created when the repository is first started.
+   * *configRootPath*: By default the configuration of each workspace is
+stored in a *workspace.xml* file within the workspace directory within
+the *rootPath* directory. If this option is specified, then the workspace
+configuration files are stored within the specified path in the virtual
+file system (see above) configured for the repository.
+   * *maxIdleTime*: By default Jackrabbit only releases resources
+associated with an opened workspace when the entire repository is closed.
+This option, if specified, sets the maximum number of seconds that a
+workspace can remain unused before the workspace is automatically closed.
+
+The workspace configuration template and all *workspace.xml*
+configuration files have the following structure:
+
+
+    <Workspace name="${wsp.name}">
+      <FileSystem .../>
+      <PersistenceManager .../>
+      <SearchIndex .../>	      <!-- optional -->
+      <ISMLocking .../>	      <!-- optional, available since 1.4 -->
+    </Workspace>
+
+
+The workspace configuration elements are:
+
+   * {{[FileSystem](#file-system-configuration.html)
+}}: The virtual file system passed to the persistence manager and search
+index.
+   * {{[PersistenceManager](#persistence-configuration.html)
+}}: Persistence configuration for workspace content.
+   * {{[SearchIndex](#search-configuration.html)
+}}: Configuration of the workspace search index.
+   * {{[ISMLocking](#item-state-locking-configuration.html)
+}}: Locking configuration for concurrent access to workspace content.
+
+{note}
+To modify the configuration of an existing workspace, you need to change
+the *workspace.xml* file of that workspace. Changing the *<Workspace/>*
+element in the repository configuration file will not affect existing
+workspaces.
+{note}
+
+<a name="JackrabbitConfiguration-Versioningconfiguration"></a>
+## Versioning configuration
+
+The version histories of all versionable nodes are stored in a
+repository-wide version store configured in the *Versioning* element of
+the repository configuration. The versioning configuration is much like
+workspace configuration as they are both used by Jackrabbit for storing
+content. The main difference between versioning and workspace configuration
+is that no search index is specified for the version store as version
+histories are indexed and searched using the repository-wide search index.
+Another difference is that there are no *$\{wsp.name\} *or
+*$\{wsp.path\} *variables for the versioning configuration. Instead the
+native file system path of the version store is explicitly specified in the
+configuration.
+
+The structure of the versioning configuration is:
+
+
+    <Versioning rootPath="${rep.home}/version">
+      <FileSystem .../>
+      <PersistenceManager .../>
+      <ISMLocking .../>	      <!-- optional, available since 1.4 -->
+    </Versioning>
+
+
+The versioning configuration elements are:
+
+   * {{[FileSystem](#file-system-configuration.html)
+}}: The virtual file system passed to the persistence manager.
+   * {{[PersistenceManager](#persistence-configuration.html)
+}}: Persistence configuration for the version store.
+   * {{[ISMLocking](#item-state-locking-configuration.html)
+}}: Locking configuration for concurrent access to workspace content.
+
+<a name="JackrabbitConfiguration-Searchconfiguration"></a>
+## Search configuration
+
+See the [Search](http://wiki.apache.org/jackrabbit/Search)
+ page on the Jackrabbit wiki.
+
+<a name="JackrabbitConfiguration-Persistenceconfiguration"></a>
+## Persistence configuration
+
+The Persistence Manager is one of the most important parts of the
+configuration, because it actually takes care of storing the nodes and
+properties. There are various very different implementations, but most of
+them are using databases to store the data. If you use a database PM and
+like to connect to an external database, you might also have to setup the
+database. This might include access rights for the Jackrabbit database user
+to allow creation of tables, because the name of the table typically
+depends on the workspace name (see the individual PM's javadoc for more
+information).
+
+For large binary properties there is the option to use the {{[DataStore](#data-store-configuration.html)
+}} instead of the Persistence Manager.
+
+For more detailed information and an overview of available PMs, see the [PersistenceManagerFAQ](http://wiki.apache.org/jackrabbit/PersistenceManagerFAQ)
+ page on the Jackrabbit wiki.
+
+{note}
+If you use a database persistence manager, the configured database
+connection *must not* be under the control of an external transaction
+manager. Jackrabbit implements distributed XA transaction support on a
+higher level, and expects to be in full control of the underlying database
+connection.
+{note}
+
+<a name="JackrabbitConfiguration-Filesystemconfiguration"></a>
+## File system configuration
+
+Early versions on Jackrabbit were designed to abstract their persistence
+mechanism using a virtual file system layer defined in the [FileSystem](http://jackrabbit.apache.org/api/1.5/org/apache/jackrabbit/core/fs/FileSystem.html)
+ interface. This low-level approach didn't work that well in practice, and
+so most of the persistence abstraction is now handled in a higher level.
+However, certain parts of Jackrabbit still use this file system
+abstraction.
+
+A virtual file system is configured in a *<FileSystem/>* bean
+configuration element. See the main file system implementations [LocalFileSystem](http://jackrabbit.apache.org/api/1.5/org/apache/jackrabbit/core/fs/local/LocalFileSystem.html)
+, [DatabaseFileSystem|http://jackrabbit.apache.org/api/1.5/org/apache/jackrabbit/core/fs/db/DatabaseFileSystem.html]
+ (including subclasses), and [MemoryFileSystem|http://jackrabbit.apache.org/api/1.5/org/apache/jackrabbit/core/fs/mem/MemoryFileSystem.html]
+ for the available options. The recommended alternative is to use the
+LocalFileSystem implementation that simply maps abstract file system
+accesses to the specified directory within the native file system.
+
+<a name="JackrabbitConfiguration-Clusterconfiguration"></a>
+## Cluster configuration
+
+See the [Clustering](http://wiki.apache.org/jackrabbit/Clustering)
+ page on the Jackrabbit wiki.
+
+<a name="JackrabbitConfiguration-Datastoreconfiguration"></a>
+## Data store configuration
+
+See the [DataStore](http://wiki.apache.org/jackrabbit/DataStore)
+ page on the Jackrabbit wiki.
+
+<a name="JackrabbitConfiguration-Itemstatelockingconfiguration"></a>
+## Item state locking configuration
+
+TODO
+
+<a name="JackrabbitConfiguration-Passwordsinconfiguration(asofJackrabbit2.3)"></a>
+## Passwords in configuration (as of Jackrabbit 2.3)
+
+When using a database-backed persistence manager or another component, you
+usually need to include the database password in Jackrabbit configuration.
+If you don't want to store such passwords in plain text inside the
+configuration file, you can encode the password in base64 and prefix it
+with "\{base64}". Jackrabbit will automatically decode such a password
+before passing it to the underlying database.
+
+As an example, the following two password configuration parameters are
+equivalent ("dGVzdA==" is the base64 encoding of "test"):
+
+
+    <param name="password" value="test"/>
+    <param name="password" value="{base64}dGVzdA=="/>
+

Added: jackrabbit/site/trunk/src/site/markdown/jackrabbit-core-1.4.1.md
URL: http://svn.apache.org/viewvc/jackrabbit/site/trunk/src/site/markdown/jackrabbit-core-1.4.1.md?rev=1670829&view=auto
==============================================================================
--- jackrabbit/site/trunk/src/site/markdown/jackrabbit-core-1.4.1.md (added)
+++ jackrabbit/site/trunk/src/site/markdown/jackrabbit-core-1.4.1.md Thu Apr  2 07:13:56 2015
@@ -0,0 +1,173 @@
+Title: jackrabbit-core 1.4.1
+Release Notes -- Apache Jackrabbit Core -- Version 1.4.1
+
+<a name="jackrabbit-core1.4.1-Introduction"></a>
+## Introduction
+
+This is the 1.4.1 patch release of the jackrabbit-core component of Apache
+Jackrabbit, a fully conforming implementation of the Content Repository for
+Java Technology API (JCR).
+
+This release fixes a binary property regression (JCR-1346) as well as other
+issues reported against the Apache Jackrabbit 1.4 release. See below for a
+full list of changes in this release.
+
+See the Apache Jackrabbit website at http://jackrabbit.apache.org/ for more
+information.
+
+<a name="jackrabbit-core1.4.1-ReleaseContents"></a>
+## Release Contents
+
+Unlike previous Jackrabbit releases that contained a full set of
+components, this patch release only contains the jackrabbit-core component.
+The component is distributed both as a source archive and a pre-compiled
+binary.
+
+*Source archive (jackrabbit-core-1.4.1-src.jar)*
+
+The source archive contains the full source code of this release in a
+"jackrabbit-core-1.4.1" directory. Use the following commands (or the
+equivalent in your environment) to build the component with Maven 2 and
+Java 1.4 or higher:
+
+
+    $ jar xf jackrabbit-core-1.4.1-src.jar
+    $ cd jackrabbit-1.4.1
+    $ mvn install
+
+
+*Pre-compiled binary (jackrabbit-core-1.4.1.jar)*
+
+Core of the Apache Jackrabbit content repository implementation.
+
+See the included README.txt file for more information.
+
+Each release file is accompanied by SHA1 and MD5 checksums and a PGP
+signature. The public key used for the signatures can be found in the KEYS
+file.
+
+<a name="jackrabbit-core1.4.1-Changesandknownissuesinthisrelease"></a>
+## Changes and known issues in this release
+
+All the changes and known issues in this release are listed below. The
+issue identifier and title is listed for each change and known issue. You
+can look up individual issues for more details in the Jackrabbit issue
+tracker at http://issues.apache.org/jira/browse/JCR
+
+Bug fixes
+
+* \[[JCR-1046](https://issues.apache.org/jira/browse/JCR-1046)
+] Non-versionable children of a versionable node should not be ...
+* \[[JCR-1227](https://issues.apache.org/jira/browse/JCR-1227)
+] Restore of empty multivalue property always changes property ...
+* \[[JCR-1305](https://issues.apache.org/jira/browse/JCR-1305)
+] JNDI data sources with BundleDbPersistenceManager: ...
+* \[[JCR-1318](https://issues.apache.org/jira/browse/JCR-1318)
+] Repository Home locked not released despite ...
+* \[[JCR-1322](https://issues.apache.org/jira/browse/JCR-1322)
+] Cluster information is not persisted to database when ...
+* \[[JCR-1323](https://issues.apache.org/jira/browse/JCR-1323)
+] When using QueryImpl.setLimit() and QueryImpl.setOffset(), ...
+* \[[JCR-1332](https://issues.apache.org/jira/browse/JCR-1332)
+] CLONE -Aggregate include ignored if no primaryType set
+* \[[JCR-1341](https://issues.apache.org/jira/browse/JCR-1341)
+] Cluster Journal directory should be created automatically
+* \[[JCR-1346](https://issues.apache.org/jira/browse/JCR-1346)
+] InternalValue.createCopy for binary properties (jcr:data) ...
+* \[[JCR-1358](https://issues.apache.org/jira/browse/JCR-1358)
+] Cluster revision file not closed on repository shutdown.
+* \[[JCR-1372](https://issues.apache.org/jira/browse/JCR-1372)
+] \[PATCH] Fix possible Null Ptr exception in ConnectionFactory
+* \[[JCR-1374](https://issues.apache.org/jira/browse/JCR-1374)
+] \[PATCH] DbDataStore: Make sure streams are closed
+* \[[JCR-1376](https://issues.apache.org/jira/browse/JCR-1376)
+] SearchIndex parameter cacheSize is ignored
+* \[[JCR-1379](https://issues.apache.org/jira/browse/JCR-1379)
+] AbstractExcerpt uses wrong logger
+* \[[JCR-1380](https://issues.apache.org/jira/browse/JCR-1380)
+] CachingHierarchyManager synchronization problem
+* \[[JCR-1389](https://issues.apache.org/jira/browse/JCR-1389)
+] setProperty("name", new Value\[0], PropertyType.LONG) loses ...
+
+Known issues
+
+* \[[JCR-43](https://issues.apache.org/jira/browse/JCR-43)
+]   Restore on nodes creates same-name-sibling of ...
+* \[[JCR-320](https://issues.apache.org/jira/browse/JCR-320)
+]  BinaryValue equals fails for two objects with ...
+* \[[JCR-392](https://issues.apache.org/jira/browse/JCR-392)
+]  Querying element by number does not work
+* \[[JCR-435](https://issues.apache.org/jira/browse/JCR-435)
+]  Node.update() does not work correct for SNS
+* \[[JCR-449](https://issues.apache.org/jira/browse/JCR-449)
+]  inconsistency in internal version items during commits
+* \[[JCR-517](https://issues.apache.org/jira/browse/JCR-517)
+]  Reserved status of namespace jcr not enforced
+* \[[JCR-522](https://issues.apache.org/jira/browse/JCR-522)
+]  XPath parser too tolerant
+* \[[JCR-537](https://issues.apache.org/jira/browse/JCR-537)
+]  Failure to remove a versionable node
+* \[[JCR-538](https://issues.apache.org/jira/browse/JCR-538)
+]  failing Node.checkin() or Node.checkout() might leave ...
+* \[[JCR-566](https://issues.apache.org/jira/browse/JCR-566)
+]  Versioning bug with restore and transactions
+* \[[JCR-575](https://issues.apache.org/jira/browse/JCR-575)
+]  unicode escapes in files generated by JJTree
+* \[[JCR-591](https://issues.apache.org/jira/browse/JCR-591)
+]  XPath position function does not work
+* \[[JCR-639](https://issues.apache.org/jira/browse/JCR-639)
+]  Allow modification of OPV=IGNORE items even if parent ...
+* \[[JCR-643](https://issues.apache.org/jira/browse/JCR-643)
+]  Own AccessManager + VersionManager : AccessDenied problem
+* \[[JCR-690](https://issues.apache.org/jira/browse/JCR-690)
+]  Nodes' and properties' names with invalid XML ...
+* \[[JCR-709](https://issues.apache.org/jira/browse/JCR-709)
+]  ArrayStoreException is thrown when jcr:deref() is used ...
+* \[[JCR-777](https://issues.apache.org/jira/browse/JCR-777)
+]  Order by clause using child axis does not throw ...
+* \[[JCR-843](https://issues.apache.org/jira/browse/JCR-843)
+]  XPath does not work with sub-axes
+* \[[JCR-908](https://issues.apache.org/jira/browse/JCR-908)
+]  Unable to properly restore a previous version of a node that ...
+* \[[JCR-932](https://issues.apache.org/jira/browse/JCR-932)
+]  Lossy SQL parsing
+* \[[JCR-935](https://issues.apache.org/jira/browse/JCR-935)
+]  ConcurrentModificationException during logout (cont'd)
+* \[[JCR-936](https://issues.apache.org/jira/browse/JCR-936)
+]  Using Oracle bundle PM throws SQL exception (cannot insert NULL)
+* \[[JCR-983](https://issues.apache.org/jira/browse/JCR-983)
+]  fn:upper accepted in too many places
+* \[[JCR-1002](https://issues.apache.org/jira/browse/JCR-1002)
+] QueryManager does not throw exception if property name ...
+* \[[JCR-1075](https://issues.apache.org/jira/browse/JCR-1075)
+] Error with predicate in query with multiple jcr:deref()
+* \[[JCR-1117](https://issues.apache.org/jira/browse/JCR-1117)
+] Bundle cache is not rolled back when the storage of a ...
+* \[[JCR-1135](https://issues.apache.org/jira/browse/JCR-1135)
+] boolean value constraints exposed in custom format
+* \[[JCR-1173](https://issues.apache.org/jira/browse/JCR-1173)
+] Session scoped lock has no effect on other cluster nodes
+* \[[JCR-1187](https://issues.apache.org/jira/browse/JCR-1187)
+] Asking a property twice for it's stream returns the same ...
+* \[[JCR-1211](https://issues.apache.org/jira/browse/JCR-1211)
+] QueryManager does not throw exception if jcr:deref is used in ...
+* \[[JCR-1223](https://issues.apache.org/jira/browse/JCR-1223)
+] Occasional NPE on node checkin
+* \[[JCR-1248](https://issues.apache.org/jira/browse/JCR-1248)
+] ParseException if search string ends with '!'
+* \[[JCR-1275](https://issues.apache.org/jira/browse/JCR-1275)
+] NullPointerException in AbstractVersionManager....
+* \[[JCR-1334](https://issues.apache.org/jira/browse/JCR-1334)
+] Deadlock with XA enabled
+* \[[JCR-1354](https://issues.apache.org/jira/browse/JCR-1354)
+] Repository shutdown reposts ERROR: failed to close connection
+* \[[JCR-1359](https://issues.apache.org/jira/browse/JCR-1359)
+] Adding nodes from concurrently running sessions cause exceptions
+* \[[JCR-1360](https://issues.apache.org/jira/browse/JCR-1360)
+] Parsing built-in CND and XML nodetypes does not result in ...
+* \[[JCR-1362](https://issues.apache.org/jira/browse/JCR-1362)
+] DatabaseJournal improperly finds tables in external schemas ...
+* \[[JCR-1367](https://issues.apache.org/jira/browse/JCR-1367)
+] Exception when closing connection under db2
+* \[[JCR-1387](https://issues.apache.org/jira/browse/JCR-1387)
+] Lock token not removed from session when node is removed

Added: jackrabbit/site/trunk/src/site/markdown/jackrabbit-core.md
URL: http://svn.apache.org/viewvc/jackrabbit/site/trunk/src/site/markdown/jackrabbit-core.md?rev=1670829&view=auto
==============================================================================
--- jackrabbit/site/trunk/src/site/markdown/jackrabbit-core.md (added)
+++ jackrabbit/site/trunk/src/site/markdown/jackrabbit-core.md Thu Apr  2 07:13:56 2015
@@ -0,0 +1,32 @@
+Title: Jackrabbit Core
+This is the Core component of the Apache Jackrabbit project. This component
+contains the core of the fully JSR 170 compliant Apache Jackrabbit content
+repository implementation.
+
+<a name="JackrabbitCore-Releases"></a>
+## Releases
+
+* May 9, 2008: jackrabbit-core 1.4.4
+* May 8, 2008: jackrabbit-core 1.4.3
+* March 26, 2008: jackrabbit-core 1.4.2
+* February 20, 2008: jackrabbit-core 1.4.1
+
+<a name="JackrabbitCore-JackrabbitDependencies"></a>
+## Jackrabbit Dependencies
+
+* [Jackrabbit API](jackrabbit-api.html)
+* [Jackrabbit JCR Commons](jackrabbit-jcr-commons.html)
+* [Jackrabbit SPI](jackrabbit-spi.html)
+* [Jackrabbit SPI Commons](jackrabbit-spi-commons.html)
+* [Jackrabbit Text Extractors](jackrabbit-text-extractors.html)
+
+<a name="JackrabbitCore-ExternalDependencies"></a>
+## External Dependencies
+
+* [JCR](jcr.html)
+* [Concurrent](concurrent.html)
+* [Commons Collections](commons-collections.html)
+* [Commons IO](commons-io.html)
+* [SLF4J API](slf4j-api.html)
+* [Lucene Core](lucene-core.html)
+* [Derby](derby.html)

Added: jackrabbit/site/trunk/src/site/markdown/jackrabbit-history.md
URL: http://svn.apache.org/viewvc/jackrabbit/site/trunk/src/site/markdown/jackrabbit-history.md?rev=1670829&view=auto
==============================================================================
--- jackrabbit/site/trunk/src/site/markdown/jackrabbit-history.md (added)
+++ jackrabbit/site/trunk/src/site/markdown/jackrabbit-history.md Thu Apr  2 07:13:56 2015
@@ -0,0 +1,114 @@
+Title: Jackrabbit History
+The Apache Jackrabbit project has a long history that is recorded in the
+archives various mailing lists, Apache board minutes, and of course also in
+the Jackrabbit codebase. This page highlights some of the key historical
+events and records from past years.
+
+For recent events, have a look at the [News Archive](news-archive.html)
+.
+
+<a name="JackrabbitHistory-Jackrabbitin2011"></a>
+## Jackrabbit in 2011
+
+* December 2011: [Jackrabbit Status December 2011](jackrabbit-status-december-2011.html)
+* September 2011: [Jackrabbit Status September 2011](jackrabbit-status-september-2011.html)
+* June 2011: [Jackrabbit Status June 2011](jackrabbit-status-june-2011.html)
+* March 2011: [Jackrabbit Status March 2011](jackrabbit-status-march-2011.html)
+
+<a name="JackrabbitHistory-Jackrabbitin2010"></a>
+## Jackrabbit in 2010
+
+* December 2010: [Jackrabbit Status December 2010](jackrabbit-status-december-2010.html)
+* December 2010: Apache Jackrabbit 2.2 [released](http://markmail.org/message/2zq6unitjdyvbiar)
+* September 2010: [Jackrabbit Status September 2010](jackrabbit-status-september-2010.html)
+* June 2010: [Jackrabbit Status June 2010](jackrabbit-status-june-2010.html)
+* April 2010: Apache Jackrabbit 2.1 [released](http://markmail.org/message/5v7aaxsctgz4vvsz)
+* March 2010: [Jackrabbit Status March 2010](jackrabbit-status-march-2010.html)
+* January 2010: Apache Jackrabbit 2.0 [released](http://markmail.org/message/oljl5ggvt725jksu)
+
+<a name="JackrabbitHistory-Jackrabbitin2009"></a>
+## Jackrabbit in 2009
+
+* December 2009: [Jackrabbit Status December 2009](jackrabbit-status-december-2009.html)
+* September 2009: [Jackrabbit Status September 2009](jackrabbit-status-september-2009.html)
+* August 2009: Apache Jackrabbit 1.6 [released](http://markmail.org/message/uojg7bkwm3cfnrvt)
+* June 2009: [Jackrabbit Status June 2009](jackrabbit-status-june-2009.html)
+* March 2009: [Jackrabbit Status March 2009](jackrabbit-status-march-2009.html)
+
+<a name="JackrabbitHistory-Jackrabbitin2008"></a>
+## Jackrabbit in 2008
+
+* December 2008: [Jackrabbit Status December 2008](jackrabbit-status-december-2008.html)
+* December 2008: Apache Jackrabbit 1.5 [released](http://markmail.org/message/ui7jard4owktrxut)
+* September 2008: [Jackrabbit Status September 2008](jackrabbit-status-september-2008.html)
+* June 2008: [Jackrabbit Status June 2008](jackrabbit-status-june-2008.html)
+* March 2008: [Jackrabbit Status March 2008](jackrabbit-status-march-2008.html)
+* January 2008: Apache Jackrabbit 1.4 [released](http://markmail.org/message/ivkdm62rp5cksap4)
+
+<a name="JackrabbitHistory-Jackrabbitin2007"></a>
+## Jackrabbit in 2007
+
+* December 2007: [Jackrabbit Status December 2007](jackrabbit-status-december-2007.html)
+* September 2007: [Jackrabbit Status September 2007](jackrabbit-status-september-2007.html)
+* June 2007: [Jackrabbit Status June 2007](jackrabbit-status-june-2007.html)
+* April 2007: Apache Jackrabbit 1.3 [released](http://markmail.org/message/fchceeuamcg4fxyw)
+* March 2007: [Jackrabbit Status March 2007](jackrabbit-status-march-2007.html)
+* January 2007: Apache Jackrabbit 1.2 [released](http://markmail.org/message/wjopzzughkzgceqr)
+
+<a name="JackrabbitHistory-Jackrabbitin2006"></a>
+## Jackrabbit in 2006
+
+* December 2006: [Jackrabbit Status December 2006](jackrabbit-status-december-2006.html)
+* October 2006: Apache Jackrabbit 1.1 [released](http://markmail.org/message/3atqtbuviomoo7dj)
+* September 2006: [Jackrabbit Status September 2006](jackrabbit-status-september-2006.html)
+* August 2006: [Jackrabbit Chair 2006 Resolution](jackrabbit-chair-2006-resolution.html)
+ makes Jukka Zitting the PMC chair 
+* July 2006: [Jackrabbit Status July 2006](jackrabbit-status-july-2006.html)
+* May 2006: [Jackrabbit Status May 2006](jackrabbit-status-may-2006.html)
+* April 2006: [Jackrabbit Status April 2006](jackrabbit-status-april-2006.html)
+* April 2006: Apache Jackrabbit 1.0 [released](http://markmail.org/message/jlk4qe336lne7v4m)
+* March 2006: The [Apache Jackrabbit Resolution](apache-jackrabbit-resolution.html)
+ makes Jackrabbit a TLP with Roy Fielding as the PMC chair
+* March 2006: [Jackrabbit Status March 2006](jackrabbit-status-march-2006.html)
+* February 2006: Apache Jackrabbit 0.9 (incubating) [released](http://markmail.org/message/7q5jhiob5wurrnpn)
+* January 2006: [Jackrabbit Status January 2006](jackrabbit-status-january-2006.html)
+
+<a name="JackrabbitHistory-Jackrabbitin2005"></a>
+## Jackrabbit in 2005
+
+* October 2005: [Jackrabbit Status October 2005](jackrabbit-status-october-2005.html)
+* July 2005: [Jackrabbit Status July 2005](jackrabbit-status-july-2005.html)
+* April 2005: [Jackrabbit Status April 2005](jackrabbit-status-april-2005.html)
+
+<a name="JackrabbitHistory-Jackrabbitin2004"></a>
+## Jackrabbit in 2004
+
+* October 2004: [Jackrabbit Status October 2004](jackrabbit-status-october-2004.html)
+* September 2004: The incubating Apache Jackrabbit project is [started](http://markmail.org/message/naqqdwlvd25d7ep6)
+* September 2004: The project is [renamed](http://markmail.org/message/mypq2iozpelmuvqh)
+ to "Jackrabbit"
+* August 2004: The [JCR Proposal](http://wiki.apache.org/incubator/JcrProposal)
+ is [accepted|http://markmail.org/message/3le75qdgvujzhv74]
+ by the Incubator PMC
+* August 2004: The idea of making the JCR RI an independent project in the
+Incubator is [discussed](http://markmail.org/message/tc3wjlmw3m6yknvx)
+* May 2004: The JCR RI [returns](http://markmail.org/message/kmhfyqm4aoc6ijxl)
+ to the Slide CVS
+* February 2004: The JCR RI codebase is [removed](http://markmail.org/message/hyt3b5intr6mj53m)
+ from Slide CVS for [various reasons|http://markmail.org/message/wt264hfdr34vr2ep]
+
+<a name="JackrabbitHistory-Jackrabbitin2003"></a>
+## Jackrabbit in 2003
+
+* February 2003: Initial version of the JCR RI codebase is [imported](http://markmail.org/message/mnhcaeifc5a6bgpb)
+ to Slide CVS
+* February 2003: The first [proposal](http://markmail.org/message/i32zkqeijec6hw37)
+ is made of making Slide the JSR 170 reference implementation
+
+<a name="JackrabbitHistory-Jackrabbitin2002"></a>
+## Jackrabbit in 2002
+
+* May 2002: Initial ideas about making Slide a JSR 170 content repository
+are [discussed](http://markmail.org/message/2gqv3a4wgjkbhieb)
+* February 2002: JSR 170 is first [mentioned](http://markmail.org/message/y2vrelkge7c3vopx)
+ on the Slide development list

Added: jackrabbit/site/trunk/src/site/markdown/jackrabbit-index-filters.md
URL: http://svn.apache.org/viewvc/jackrabbit/site/trunk/src/site/markdown/jackrabbit-index-filters.md?rev=1670829&view=auto
==============================================================================
--- jackrabbit/site/trunk/src/site/markdown/jackrabbit-index-filters.md (added)
+++ jackrabbit/site/trunk/src/site/markdown/jackrabbit-index-filters.md Thu Apr  2 07:13:56 2015
@@ -0,0 +1,3 @@
+Title: Jackrabbit Index Filters
+The Jackrabbit Index Filters component has been replaced by the new [Jackrabbit Text Extractors](jackrabbit-text-extractors.html)
+ component.

Added: jackrabbit/site/trunk/src/site/markdown/jackrabbit-jca-resource-adapter.md
URL: http://svn.apache.org/viewvc/jackrabbit/site/trunk/src/site/markdown/jackrabbit-jca-resource-adapter.md?rev=1670829&view=auto
==============================================================================
--- jackrabbit/site/trunk/src/site/markdown/jackrabbit-jca-resource-adapter.md (added)
+++ jackrabbit/site/trunk/src/site/markdown/jackrabbit-jca-resource-adapter.md Thu Apr  2 07:13:56 2015
@@ -0,0 +1,8 @@
+Title: Jackrabbit JCA Resource Adapter
+This is the JCA Resource Adapter component of the Apache Jackrabbit
+project. This component packages the Jackrabbit content repository as a JCA
+1.0 resource adapter. The packaged adapter can be deployed on a wide range
+of application servers.
+
+The Jackrabbit content repository embedded in the JCA package is started
+when first accessed and shut down when the adapter is un- or re-deployed.

Added: jackrabbit/site/trunk/src/site/markdown/jackrabbit-jcr-client.md
URL: http://svn.apache.org/viewvc/jackrabbit/site/trunk/src/site/markdown/jackrabbit-jcr-client.md?rev=1670829&view=auto
==============================================================================
--- jackrabbit/site/trunk/src/site/markdown/jackrabbit-jcr-client.md (added)
+++ jackrabbit/site/trunk/src/site/markdown/jackrabbit-jcr-client.md Thu Apr  2 07:13:56 2015
@@ -0,0 +1,7 @@
+Title: Jackrabbit JCR Client
+This is the JCR Client component of the Apache Jackrabbit project.
+
+<a name="JackrabbitJCRClient-APIdocumentation"></a>
+## API documentation
+
+* [jackrabbit-jcr-client 2.2](http://jackrabbit.apache.org/api/2.2/org/apache/jackrabbit/client/package-summary.html)

Added: jackrabbit/site/trunk/src/site/markdown/jackrabbit-jcr-commons.md
URL: http://svn.apache.org/viewvc/jackrabbit/site/trunk/src/site/markdown/jackrabbit-jcr-commons.md?rev=1670829&view=auto
==============================================================================
--- jackrabbit/site/trunk/src/site/markdown/jackrabbit-jcr-commons.md (added)
+++ jackrabbit/site/trunk/src/site/markdown/jackrabbit-jcr-commons.md Thu Apr  2 07:13:56 2015
@@ -0,0 +1,4 @@
+Title: Jackrabbit JCR Commons
+This is the JCR Commons component of the Apache Jackrabbit project. This
+component contains a number of general-purpose classes for use with the JCR
+API.

Added: jackrabbit/site/trunk/src/site/markdown/jackrabbit-jcr-rmi.md
URL: http://svn.apache.org/viewvc/jackrabbit/site/trunk/src/site/markdown/jackrabbit-jcr-rmi.md?rev=1670829&view=auto
==============================================================================
--- jackrabbit/site/trunk/src/site/markdown/jackrabbit-jcr-rmi.md (added)
+++ jackrabbit/site/trunk/src/site/markdown/jackrabbit-jcr-rmi.md Thu Apr  2 07:13:56 2015
@@ -0,0 +1,77 @@
+Title: Jackrabbit JCR-RMI
+This is the JCR-RMI component of the Apache Jackrabbit project. JCR-RMI is
+a transparent Remote Method Invocation (RMI) layer for the Content
+Repository for Java Technology API (JCR). The layer makes it possible to
+remotely access JCR content repositories and is compatible with all JCR
+implementations.
+
+<a name="JackrabbitJCR-RMI-Settinguparemoterepository"></a>
+### Setting up a remote repository
+
+Setting up the server part of the JCR-RMI layer is quite straightforward.
+After instantiating a local JCR repository you need to wrap it into a
+remote adapter and create an RMI binding for the repository. A variation of
+the following code is usually all that is needed in addition to the
+standard RMI setup (starting rmiregistry, etc.):
+
+
+    Repository repository = ...; // The local repository
+    String name = ...; // The RMI URL for the repository
+        
+    RemoteAdapterFactory factory = new ServerAdapterFactory();
+    RemoteRepository remote = factory.getRemoteRepository(repository);
+    Naming.bind(name, remote);  // Make the RMI binding using java.rmi.Naming
+
+
+<a name="JackrabbitJCR-RMI-Accessingaremoterepository"></a>
+### Accessing a remote repository
+
+The ClientRepositoryFactory class provides a convenient mechanism for
+looking up a remote JCR-RMI repository. The factory can be used either
+directly or as a JNDI object factory.
+
+The following example shows how to use the ClientRepositoryFactory
+directly:
+
+
+    String name = ...; // The RMI URL of the repository
+        
+    ClientRepositoryFactory factory = new ClientRepositoryFactory();
+    Repository repository = factory.getRepository(name);
+
+
+The ClientRepositoryFactory can also be used via JNDI. The following
+example settings and code demonstrate how to configure and use the
+transparent JCR-RMI layer in a Tomcat 5.5 web application:
+
+context.xml:
+
+
+    <Resource name="jcr/Repository" auth="Container"
+    	  type="javax.jcr.Repository"
+    	 
+factory="org.apache.jackrabbit.rmi.client.ClientRepositoryFactory"
+    	  url="..."/>
+
+
+web.xml:
+
+
+    <resource-env-ref>
+      <description>The external content repository</description>
+      <resource-env-ref-name>jcr/Repository</resource-env-ref-name>
+      <resource-env-ref-type>javac.jcr.Repository</resource-env-ref-type>
+    </resource-env-ref>
+
+
+...SomeServlet.java:
+
+
+    Context initial = new InitialContext();
+    Context context = (Context) initial.lookup("java:comp/env");
+    Repository repository = (Repository) context.lookup("jcr/Repository");
+
+
+Note that in the example above only the context.xml configuration file
+contains a direct references to the JCR-RMI layer. All other parts of the
+web application can be implemented using the standard JCR interfaces. 

Added: jackrabbit/site/trunk/src/site/markdown/jackrabbit-jcr-server.md
URL: http://svn.apache.org/viewvc/jackrabbit/site/trunk/src/site/markdown/jackrabbit-jcr-server.md?rev=1670829&view=auto
==============================================================================
--- jackrabbit/site/trunk/src/site/markdown/jackrabbit-jcr-server.md (added)
+++ jackrabbit/site/trunk/src/site/markdown/jackrabbit-jcr-server.md Thu Apr  2 07:13:56 2015
@@ -0,0 +1,55 @@
+Title: Jackrabbit JCR Server
+This is the JCR Server component of the Apache Jackrabbit project. This
+component contains two WebDAV based JCR server implementations:
+* Simple Webdav Server
+* JCR Webdav Server
+
+<a name="JackrabbitJCRServer-SimpleWebdavServer"></a>
+### Simple Webdav Server
+
+WebDAV (conformance levels 1, 2, and 3) and DeltaV compliant WebDAV server
+implementation to access a JSR170 repository.
+
+Futher information such as configuration as well as the
+_SimpleWebdavServlet.java_ itself can be found in the [Jackrabbit Web Application](jackrabbit-web-application.html)
+ project.
+* Packages:
+<table>
+<tr><td> org.apache.jackrabbit.server </td><td> Common server functionality </td></tr>
+<tr><td> org.apache.jackrabbit.server.io </td><td> Import and export facilities </td></tr>
+<tr><td> org.apache.jackrabbit.webdav.simple </td><td> Server side WebDAV implementation
+(DavResource, ResourceConfig,...). </td></tr>
+* Servlet:
+<tr><td> org.apache.jackrabbit.j2ee.SimpleWebdavServlet.java </td><td> see [Jackrabbit Web Application](jackrabbit-web-application.html)
+ </td></tr>
+</table>
+
+Note thatn when run on top of a JCR 2.0 implementation that also supports
+shareable nodes, the WebDAV BIND specification
+([http://tools.ietf.org/html/draft-ietf-webdav-bind](http://tools.ietf.org/html/draft-ietf-webdav-bind)
+) is also supported.
+
+<a name="JackrabbitJCRServer-JCRWebdavServer"></a>
+### JCR Webdav Server
+
+Server used to remote JSR170 calls via WebDAV.
+
+The client counterpart of this server is represented by the JCR to SPI
+project in combination with the _SPI to WebDAV_ SPI implementation that can
+be found in the [Jackrabbit SPI to DAV](jackrabbit-spi-to-dav.html)
+ project. Easy to use setup of both components can be found in [Jackrabbit JCR to DAV]
+ and [Jackrabbit JCR Client]
+, respectively.
+* Packages:
+<table>
+<tr><td> org.apache.jackrabbit.server </td><td> Common server functionality </td></tr>
+<tr><td> org.apache.jackrabbit.server.jcr </td><td> JCR-Server </td></tr>
+<tr><td> org.apache.jackrabbit.webdav.jcr </td><td> Server side WebDAV implementation
+(DavResources, Reports, Properties) </td></tr>
+* Servlet:
+<tr><td> org.apache.jackrabbit.j2ee.JCRServerServlet.java </td><td> see [Jackrabbit Web Application](jackrabbit-web-application.html)
+</td></tr>
+</table>
+
+Further reading:
+* http://jackrabbit.apache.org/JCR_Webdav_Protocol.doc

Added: jackrabbit/site/trunk/src/site/markdown/jackrabbit-jcr-servlet.md
URL: http://svn.apache.org/viewvc/jackrabbit/site/trunk/src/site/markdown/jackrabbit-jcr-servlet.md?rev=1670829&view=auto
==============================================================================
--- jackrabbit/site/trunk/src/site/markdown/jackrabbit-jcr-servlet.md (added)
+++ jackrabbit/site/trunk/src/site/markdown/jackrabbit-jcr-servlet.md Thu Apr  2 07:13:56 2015
@@ -0,0 +1,6 @@
+Title: Jackrabbit JCR Servlet
+This is the JCR Servlet component of the Apache Jackrabbit project. This
+component contains a set of servlets and other classes designed to make it
+easier to use Jackrabbit and other JCR content repositories in web
+applications.
+

Added: jackrabbit/site/trunk/src/site/markdown/jackrabbit-jcr-tests.md
URL: http://svn.apache.org/viewvc/jackrabbit/site/trunk/src/site/markdown/jackrabbit-jcr-tests.md?rev=1670829&view=auto
==============================================================================
--- jackrabbit/site/trunk/src/site/markdown/jackrabbit-jcr-tests.md (added)
+++ jackrabbit/site/trunk/src/site/markdown/jackrabbit-jcr-tests.md Thu Apr  2 07:13:56 2015
@@ -0,0 +1,6 @@
+Title: Jackrabbit JCR Tests
+This is the JCR Tests component of the Apache Jackrabbit project. This
+component contains a set of JCR API test cases designed for testing the
+compliance of an implementation. Note that although this code base is used
+also for the official JCR TCK, this is not the official TCK and passing the
+test of this component can not be used as an indication of API compliance.

Added: jackrabbit/site/trunk/src/site/markdown/jackrabbit-jcr-to-dav.md
URL: http://svn.apache.org/viewvc/jackrabbit/site/trunk/src/site/markdown/jackrabbit-jcr-to-dav.md?rev=1670829&view=auto
==============================================================================
--- jackrabbit/site/trunk/src/site/markdown/jackrabbit-jcr-to-dav.md (added)
+++ jackrabbit/site/trunk/src/site/markdown/jackrabbit-jcr-to-dav.md Thu Apr  2 07:13:56 2015
@@ -0,0 +1,7 @@
+Title: Jackrabbit JCR to DAV
+This is the JCR2DAV component of the Apache Jackrabbit project.
+
+<a name="JackrabbitJCRtoDAV-APIdocumentation"></a>
+## API documentation
+
+* [jackrabbit-jcr2dav 2.2](http://jackrabbit.apache.org/api/2.2/org/apache/jackrabbit/jcr2dav/package-summary.html)

Added: jackrabbit/site/trunk/src/site/markdown/jackrabbit-jcr-to-spi.md
URL: http://svn.apache.org/viewvc/jackrabbit/site/trunk/src/site/markdown/jackrabbit-jcr-to-spi.md?rev=1670829&view=auto
==============================================================================
--- jackrabbit/site/trunk/src/site/markdown/jackrabbit-jcr-to-spi.md (added)
+++ jackrabbit/site/trunk/src/site/markdown/jackrabbit-jcr-to-spi.md Thu Apr  2 07:13:56 2015
@@ -0,0 +1,17 @@
+Title: Jackrabbit JCR to SPI
+This is the JCR to SPI component of the Apache Jackrabbit project. It
+provides and exposes the JCR API to the application and is a consumer of an
+implementation of the [SPI interfaces](jackrabbit-spi.html)
+.
+
+Jackrabbit JCR to SPI is intended to act as a generic implementation of the
+transient component that is layered on top of the persistent state of the
+JCR repository. The latter is is represented by the SPI implementation.
+
+This means that JCR to SPI handles
+
+    * transient storage of pending changes.
+    * resolution of namespaces to prefixes.
+    * Session-local namespace mappings.
+    * Session-mediated XML import.
+    * XML export.

Added: jackrabbit/site/trunk/src/site/markdown/jackrabbit-ocm-node-management.md
URL: http://svn.apache.org/viewvc/jackrabbit/site/trunk/src/site/markdown/jackrabbit-ocm-node-management.md?rev=1670829&view=auto
==============================================================================
--- jackrabbit/site/trunk/src/site/markdown/jackrabbit-ocm-node-management.md (added)
+++ jackrabbit/site/trunk/src/site/markdown/jackrabbit-ocm-node-management.md Thu Apr  2 07:13:56 2015
@@ -0,0 +1,4 @@
+Title: Jackrabbit OCM Node Management
+This is the OCM node type management component of the Apache Jackrabbit
+project. This component simplifies registration of node types and
+namespaces referenced in OCM mapping descriptors.

Added: jackrabbit/site/trunk/src/site/markdown/jackrabbit-ocm.md
URL: http://svn.apache.org/viewvc/jackrabbit/site/trunk/src/site/markdown/jackrabbit-ocm.md?rev=1670829&view=auto
==============================================================================
--- jackrabbit/site/trunk/src/site/markdown/jackrabbit-ocm.md (added)
+++ jackrabbit/site/trunk/src/site/markdown/jackrabbit-ocm.md Thu Apr  2 07:13:56 2015
@@ -0,0 +1,9 @@
+Title: Jackrabbit OCM
+This Jackrabbit subproject is an object/JCR persistence and query service.
+This tools lets you to persist Java objects into a JCR compliant repository
+- including association, inheritance, polymorphism, composition, and the
+Java Collections framework.
+
+Furthermore, this object-content mapping component allows you to express
+queries with Java-based criteria, as well as in JCR query language. It
+offers also features like version support and object locking.

Added: jackrabbit/site/trunk/src/site/markdown/jackrabbit-roadmap.md
URL: http://svn.apache.org/viewvc/jackrabbit/site/trunk/src/site/markdown/jackrabbit-roadmap.md?rev=1670829&view=auto
==============================================================================
--- jackrabbit/site/trunk/src/site/markdown/jackrabbit-roadmap.md (added)
+++ jackrabbit/site/trunk/src/site/markdown/jackrabbit-roadmap.md Thu Apr  2 07:13:56 2015
@@ -0,0 +1,53 @@
+Title: Jackrabbit Roadmap
+This is a roadmap of future Apache Jackrabbit releases and features. See [the dev@ list](mailing-lists.html)
+ for the latest status.
+
+<a name="JackrabbitRoadmap-Unstable/stablereleasemodel"></a>
+## Unstable/stable release model
+
+Starting with Jackrabbit 2.3 we are adopting a "Linux-style"
+unstable/stable release model with odd/even minor version numbers used to
+mark the status of a release.
+
+* [Jackrabbit 2.3 (trunk)](https://svn.apache.org/repos/asf/jackrabbit/trunk/)
+ ([download|Downloads#v23])
+
+Unstable 2.3.x releases will be cut fairly frequently directly from
+Jackrabbit trunk, and a stable 2.4 release branch will be created later on.
+At current rate it looks like the 2.4 branch can be created before the end
+of 2011.
+
+Once the 2.4 branch has been created, trunk will switch to 2.5.x and
+continue progressing towards 2.6, etc.
+
+<a name="JackrabbitRoadmap-Maintenancebranches"></a>
+## Maintenance branches
+
+We currently support the following maintenance branches:
+
+* [Jackrabbit 2.2](https://svn.apache.org/repos/asf/jackrabbit/branches/2.2/)
+ ([download|Downloads#v22])
+* [Jackrabbit 2.1](https://svn.apache.org/repos/asf/jackrabbit/branches/2.1/)
+ ([download|Downloads#v21])
+* [Jackrabbit 2.0](https://svn.apache.org/repos/asf/jackrabbit/branches/2.0/)
+ ([download|Downloads#v20])
+
+<a name="JackrabbitRoadmap-Endoflife"></a>
+## End of life
+
+The Jackrabbit 1.6 maintenance branch has reached its end of life status.
+No more patch releases will be cut from the 1.6 branch, and the latest
+1.6.5 release will be archived in December 2011.
+
+* [Jackrabbit 1.6](https://svn.apache.org/repos/asf/jackrabbit/branches/1.6/)
+ ([download|Downloads#v16])
+
+There is currently no schedule for declaring the end of life of any of the
+stable 2.x maintenance branches.
+
+<a name="JackrabbitRoadmap-Prototypingthefuture"></a>
+## Prototyping the future
+
+The ongoing microkernel work in the Jackrabbit sandbox is being used to
+prototype a possible next generation architecture for a future major new
+Jackrabbit release.