You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jackrabbit.apache.org by mr...@apache.org on 2022/12/15 09:54:28 UTC
svn commit: r1906010 [8/22] - in /jackrabbit/site/live/jcr: ./ components/ css/ fonts/ js/ ocm/ status/
Modified: jackrabbit/site/live/jcr/issue-tracker.html
URL: http://svn.apache.org/viewvc/jackrabbit/site/live/jcr/issue-tracker.html?rev=1906010&r1=1906009&r2=1906010&view=diff
==============================================================================
--- jackrabbit/site/live/jcr/issue-tracker.html (original)
+++ jackrabbit/site/live/jcr/issue-tracker.html Thu Dec 15 09:54:26 2022
@@ -1,42 +1,40 @@
<!DOCTYPE html>
+
+
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.9.2 from src\site\markdown/issue-tracker.md at 2022-05-12
- | Rendered using Apache Maven Fluido Skin 1.9
+ | Generated by Apache Maven Doxia Site Renderer 1.11.1 from src/site/markdown/issue-tracker.md at 2022-12-15
+ | Rendered using Apache Maven Fluido Skin 1.11.1
-->
<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 1.9.2" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 1.11.1" />
<title>Apache Jackrabbit – Issue Tracker</title>
- <link rel="stylesheet" href="./css/apache-maven-fluido-1.9.min.css" />
+ <link rel="stylesheet" href="./css/apache-maven-fluido-1.11.1.min.css" />
<link rel="stylesheet" href="./css/site.css" />
<link rel="stylesheet" href="./css/print.css" media="print" />
- <script src="./js/apache-maven-fluido-1.9.min.js"></script>
-<!-- Matomo -->
-<script>
- var _paq = window._paq = window._paq || [];
- /* tracker methods like "setCustomDimension" should be called before "trackPageView" */
- /* We explicitly disable cookie tracking to avoid privacy issues */
- _paq.push(['disableCookies']);
- _paq.push(['trackPageView']);
- _paq.push(['enableLinkTracking']);
- (function() {
- var u="https://matomo.privacy.apache.org/";
- _paq.push(['setTrackerUrl', u+'matomo.php']);
- _paq.push(['setSiteId', '4']);
- var d=document, g=d.createElement('script'), s=d.getElementsByTagName('script')[0];
- g.async=true; g.src=u+'matomo.js'; s.parentNode.insertBefore(g,s);
- })();
-</script>
-<!-- End Matomo Code -->
+ <script src="./js/apache-maven-fluido-1.11.1.min.js"></script>
+
+ <!-- Matomo -->
+ <script>
+ var _paq = window._paq = window._paq || [];
+ _paq.push(['disableCookies']);
+ _paq.push(['trackPageView']);
+ _paq.push(['enableLinkTracking']);
+
+ (function() {
+ var u="https://analytics.apache.org";
+ _paq.push(['setTrackerUrl', u+'/matomo.php']);
+ _paq.push(['setSiteId', '4']);
+ var d=document, g=d.createElement('script'), s=d.getElementsByTagName('script')[0];
+ g.async=true; g.src=u+'/matomo.js'; s.parentNode.insertBefore(g,s);
+ })();
+ </script>
+ <!-- End Matomo Code -->
</head>
<body class="topBarEnabled">
- <a href="https://github.com/apache/jackrabbit">
- <img style="position: absolute; top: 0; right: 0; border: 0; z-index: 10000;"
- src="https://s3.amazonaws.com/github/ribbons/forkme_right_red_aa0000.png"
- alt="Fork me on GitHub">
- </a>
+ <a class="github-fork-ribbon right-top" href="https://github.com/apache/jackrabbit" data-ribbon="Fork me on GitHub" title="Fork me on GitHub">Fork me on GitHub</a>
<header id="topbar" class="navbar navbar-fixed-top ">
<div class="navbar-inner">
<div class="container-fluid">
@@ -49,7 +47,7 @@
</a>
<ul class="nav">
<li class="dropdown">
- <a href="#" class="dropdown-toggle" data-toggle="dropdown">Apache Jackrabbit <b class="caret"></b></a>
+ <a class="dropdown-toggle" data-toggle="dropdown">Apache Jackrabbit <b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="index.html" title="Welcome">Welcome</a></li>
<li><a href="downloads.html" title="Downloads">Downloads</a></li>
@@ -60,7 +58,7 @@
</ul>
</li>
<li class="dropdown">
- <a href="#" class="dropdown-toggle" data-toggle="dropdown">Documentation <b class="caret"></b></a>
+ <a class="dropdown-toggle" data-toggle="dropdown">Documentation <b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="getting-started-with-apache-jackrabbit.html" title="Getting Started">Getting Started</a></li>
<li><a href="standalone-server.html" title="Standalone Server">Standalone Server</a></li>
@@ -75,13 +73,13 @@
</ul>
</li>
<li class="dropdown">
- <a href="#" class="dropdown-toggle" data-toggle="dropdown">Development <b class="caret"></b></a>
+ <a class="dropdown-toggle" data-toggle="dropdown">Development <b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="jackrabbit-team.html" title="Jackrabbit Team">Jackrabbit Team</a></li>
<li><a href="jackrabbit-roadmap.html" title="Jackrabbit Roadmap">Jackrabbit Roadmap</a></li>
<li><a href="building-jackrabbit.html" title="Building Jackrabbit">Building Jackrabbit</a></li>
<li><a href="mailing-lists.html" title="Mailing Lists">Mailing Lists</a></li>
- <li><a href="issue-tracker.html" title="Issue Tracker">Issue Tracker</a></li>
+ <li><a title="Issue Tracker">Issue Tracker</a></li>
<li><a href="source-repository.html" title="Source Repository">Source Repository</a></li>
<li><a href="continuous-integration.html" title="Continuous Integration">Continuous Integration</a></li>
<li><a href="website.html" title="Website">Website</a></li>
@@ -90,7 +88,7 @@
</ul>
</li>
<li class="dropdown">
- <a href="#" class="dropdown-toggle" data-toggle="dropdown">Apache Software Foundation <b class="caret"></b></a>
+ <a class="dropdown-toggle" data-toggle="dropdown">Apache Software Foundation <b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="https://www.apache.org/foundation/how-it-works.html" title="Introduction">Introduction</a></li>
<li><a href="https://www.apache.org/foundation/sponsorship.html" title="Sponsorship">Sponsorship</a></li>
@@ -105,7 +103,7 @@
<div class="container-fluid">
<header>
<div id="banner">
- <div class="pull-left"><div id="bannerLeft"><h2>Apache Jackrabbit Site</h2>
+ <div class="pull-left"><div id="bannerLeft"><h1>Apache Jackrabbit Site</h1>
</div>
</div>
<div class="pull-right"></div>
@@ -114,7 +112,7 @@
<div id="breadcrumbs">
<ul class="breadcrumb">
- <li id="publishDate">Last Published: 2022-05-12</li>
+ <li id="publishDate">Last Published: 2022-12-15</li>
</ul>
</div>
</header>
@@ -145,7 +143,7 @@
<li><a href="jackrabbit-roadmap.html" title="Jackrabbit Roadmap"><span class="none"></span>Jackrabbit Roadmap</a></li>
<li><a href="building-jackrabbit.html" title="Building Jackrabbit"><span class="none"></span>Building Jackrabbit</a></li>
<li><a href="mailing-lists.html" title="Mailing Lists"><span class="none"></span>Mailing Lists</a></li>
- <li class="active"><a href="#"><span class="none"></span>Issue Tracker</a></li>
+ <li class="active"><a><span class="none"></span>Issue Tracker</a></li>
<li><a href="source-repository.html" title="Source Repository"><span class="none"></span>Source Repository</a></li>
<li><a href="continuous-integration.html" title="Continuous Integration"><span class="none"></span>Continuous Integration</a></li>
<li><a href="website.html" title="Website"><span class="none"></span>Website</a></li>
@@ -159,7 +157,6 @@
</ul>
</nav>
<div class="well sidebar-nav">
- <hr />
<div id="poweredBy">
<div class="clear"></div>
<div class="clear"></div>
@@ -186,14 +183,43 @@
limitations under the License.
-->
<h1>Issue Tracker</h1>
-<p>Apache Jackrabbit uses Jira for tracking bug reports and requests for improvements, new features, and other changes.</p>
-<p>The issue tracker is available at <a class="externalLink" href="https://issues.apache.org/jira/browse/JCR">https://issues.apache.org/jira/browse/JCR</a> and <a class="externalLink" href="https://issues.apache.org/jira/browse/OAK">https://issues.apache.org/jira/browse/OAK</a> and is readable by everyone. A Jira account is needed to create new issues and to comment on existing issues. Use the <a class="externalLink" href="https://issues.apache.org/jira/secure/Signup!default.jspa">registration form</a> to request an account if you do not already have one.</p><section>
+<p>Apache Jackrabbit uses Jira for tracking bug reports and requests for
+improvements, new features, and other changes.</p>
+<p>The issue tracker is available at <a class="externalLink" href="https://issues.apache.org/jira/browse/JCR">https://issues.apache.org/jira/browse/JCR</a>
+and <a class="externalLink" href="https://issues.apache.org/jira/browse/OAK">https://issues.apache.org/jira/browse/OAK</a>
+and is readable by everyone. A Jira account is needed to create new issues
+and to comment on existing issues. Use the <a class="externalLink" href="https://issues.apache.org/jira/secure/Signup!default.jspa">registration form</a>
+to request an account if you do not already have one.</p><section>
<h2><a name="Issue_workflow"></a>Issue workflow</h2>
-<p>When an issue is created, it’s in the <i>Open</i> 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 <i>Patch available</i> state to give it more visibility. If the patch is cancelled because more work is needed, the issue moves back to the <i>Open</i> state.</p>
-<p>Once the issue is solved, the committer who committed the changes marks the issue as <i>Resolved</i> with resolution type <i>Fixed</i>. Other resolution types like <i>Duplicate</i>, <i>Invalid</i> or <i>Won’t Fix</i> are used when resolving issues that for one reason or another require no changes in the codebase. An issue can be <i>Reopened</i> if the committed fix is found to be not good enough.</p>
-<p>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 <code>svn merge -c _revision_ ^/jackrabbit/trunk</code> 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 (once the backport is done, not before that!). Note that this field is used to generate release notes, thus it needs to be maintained properly.</p>
-<p>Finally, once a release containing the change has been made, the release manager will mark the issue <i>Closed</i>, 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.</p>
-<p>If a fix has not been backported yet, but should be considered for the next release of a maintenance branch, it can be labeled as “candidate_branchname” (or “candidate_oak_branchname”). Once the backport for that maintenance branch has been done, the label should be removed (or replaced by a label for the next older maintenance branch).</p></section><section>
+<p>When an issue is created, it's in the <i>Open</i> 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
+<i>Patch available</i> state to give it more visibility. If the patch is
+cancelled because more work is needed, the issue moves back to the <i>Open</i>
+state.</p>
+<p>Once the issue is solved, the committer who committed the changes marks the
+issue as <i>Resolved</i> with resolution type <i>Fixed</i>. Other resolution types
+like <i>Duplicate</i>, <i>Invalid</i> or <i>Won't Fix</i> are used when resolving issues
+that for one reason or another require no changes in the codebase. An issue
+can be <i>Reopened</i> if the committed fix is found to be not good enough.</p>
+<p>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 <code>svn merge -c _revision_ ^/jackrabbit/trunk</code> 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 (once the backport is done, not before that!). Note that
+this field is used to generate release notes, thus it needs to be maintained
+properly.</p>
+<p>Finally, once a release containing the change has been made, the release
+manager will mark the issue <i>Closed</i>, 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.</p>
+<p>If a fix has not been backported yet, but should be considered for the next
+release of a maintenance branch, it can be labeled as “candidate_branchname” (or
+“candidate_oak_branchname”). Once the backport for that maintenance branch
+has been done, the label should be removed (or replaced by a label for the next
+older maintenance branch).</p></section><section>
<h2><a name="Issue_contents"></a>Issue contents</h2>
<p>See below for guidelines on how to use the various fields in an issue.</p><section>
<h3><a name="Issue_type"></a>Issue type</h3>
@@ -202,54 +228,57 @@
<thead>
<tr class="a">
-<th> Issue type </th>
-<th> Description </th></tr>
+<th>Issue type</th>
+<th>Description</th></tr>
</thead><tbody>
<tr class="b">
-<td> <i>Bug</i> </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 <a href="mailing-lists.html">mailing lists</a> first for help.</td></tr>
+<td align="left"><i>Bug</i></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 <a href="mailing-lists.html">mailing lists</a> first for help.</td></tr>
<tr class="a">
-<td> <i>New Feature</i> </td>
-<td> Use a feature request when Jackrabbit does not have some functionality you need.</td></tr>
+<td align="left"><i>New Feature</i></td>
+<td>Use a feature request when Jackrabbit does not have some functionality you need.</td></tr>
<tr class="b">
-<td> <i>Improvement</i> </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>
+<td align="left"><i>Improvement</i></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 class="a">
-<td> <i>Test</i> </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>
+<td align="left"><i>Test</i></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 class="b">
-<td> <i>Task</i> </td>
-<td> Used only for issues related to project infrastructure.</td></tr>
+<td align="left"><i>Task</i></td>
+<td>Used only for issues related to project infrastructure.</td></tr>
</tbody>
</table></section><section>
<h3><a name="Issue_summary.2C_environment_and_description"></a>Issue summary, environment and description</h3>
-<p>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.</p></section><section>
+<p>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.</p></section><section>
<h3><a name="Issue_priority"></a>Issue priority</h3>
<p>Issue priority should be set according to the following:</p>
<table border="0" class="table table-striped">
<thead>
<tr class="a">
-<th> Issue priority </th>
-<th> Description</th></tr>
+<th>Issue priority</th>
+<th>Description</th></tr>
</thead><tbody>
<tr class="b">
-<td> <i>Blocker</i> </td>
-<td> Legal or other fundamental issue that makes it impossible to release Jackrabbit code</td></tr>
+<td align="left"><i>Blocker</i></td>
+<td>Legal or other fundamental issue that makes it impossible to release Jackrabbit code</td></tr>
<tr class="a">
-<td> <i>Critical</i> </td>
-<td> Major loss of functionality that affects many Jackrabbit users</td></tr>
+<td align="left"><i>Critical</i></td>
+<td>Major loss of functionality that affects many Jackrabbit users</td></tr>
<tr class="b">
-<td> <i>Major</i> </td>
-<td> Important issue that should be resolved soon</td></tr>
+<td align="left"><i>Major</i></td>
+<td>Important issue that should be resolved soon</td></tr>
<tr class="a">
-<td> <i>Minor</i> </td>
-<td> Nice to have issues</td></tr>
+<td align="left"><i>Minor</i></td>
+<td>Nice to have issues</td></tr>
<tr class="b">
-<td> <i>Trivial</i> </td>
-<td> Trivial changes that can be applied whenever someone has extra time</td></tr>
+<td align="left"><i>Trivial</i></td>
+<td>Trivial changes that can be applied whenever someone has extra time</td></tr>
</tbody>
</table></section></section>
</main>
@@ -263,10 +292,12 @@
<a href="https://www.apache.org/">The Apache Software Foundation</a> | <a href="https://privacy.apache.org/policies/privacy-policy-public.html">Privacy Policy</a>
</p>
</div>
- <div id="ohloh" class="pull-right">
- <script src="https://www.ohloh.net/p/jackrabbit/widgets/project_users_logo.js"></script>
- </div>
- </div>
+ </div>
</footer>
+<script>
+ if(anchors) {
+ anchors.add();
+ }
+</script>
</body>
</html>
\ No newline at end of file
Modified: jackrabbit/site/live/jcr/jackrabbit-architecture.html
URL: http://svn.apache.org/viewvc/jackrabbit/site/live/jcr/jackrabbit-architecture.html?rev=1906010&r1=1906009&r2=1906010&view=diff
==============================================================================
--- jackrabbit/site/live/jcr/jackrabbit-architecture.html (original)
+++ jackrabbit/site/live/jcr/jackrabbit-architecture.html Thu Dec 15 09:54:26 2022
@@ -1,42 +1,40 @@
<!DOCTYPE html>
+
+
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.9.2 from src\site\markdown/jackrabbit-architecture.md at 2022-05-12
- | Rendered using Apache Maven Fluido Skin 1.9
+ | Generated by Apache Maven Doxia Site Renderer 1.11.1 from src/site/markdown/jackrabbit-architecture.md at 2022-12-15
+ | Rendered using Apache Maven Fluido Skin 1.11.1
-->
<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 1.9.2" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 1.11.1" />
<title>Apache Jackrabbit – Jackrabbit Architecture</title>
- <link rel="stylesheet" href="./css/apache-maven-fluido-1.9.min.css" />
+ <link rel="stylesheet" href="./css/apache-maven-fluido-1.11.1.min.css" />
<link rel="stylesheet" href="./css/site.css" />
<link rel="stylesheet" href="./css/print.css" media="print" />
- <script src="./js/apache-maven-fluido-1.9.min.js"></script>
-<!-- Matomo -->
-<script>
- var _paq = window._paq = window._paq || [];
- /* tracker methods like "setCustomDimension" should be called before "trackPageView" */
- /* We explicitly disable cookie tracking to avoid privacy issues */
- _paq.push(['disableCookies']);
- _paq.push(['trackPageView']);
- _paq.push(['enableLinkTracking']);
- (function() {
- var u="https://matomo.privacy.apache.org/";
- _paq.push(['setTrackerUrl', u+'matomo.php']);
- _paq.push(['setSiteId', '4']);
- var d=document, g=d.createElement('script'), s=d.getElementsByTagName('script')[0];
- g.async=true; g.src=u+'matomo.js'; s.parentNode.insertBefore(g,s);
- })();
-</script>
-<!-- End Matomo Code -->
+ <script src="./js/apache-maven-fluido-1.11.1.min.js"></script>
+
+ <!-- Matomo -->
+ <script>
+ var _paq = window._paq = window._paq || [];
+ _paq.push(['disableCookies']);
+ _paq.push(['trackPageView']);
+ _paq.push(['enableLinkTracking']);
+
+ (function() {
+ var u="https://analytics.apache.org";
+ _paq.push(['setTrackerUrl', u+'/matomo.php']);
+ _paq.push(['setSiteId', '4']);
+ var d=document, g=d.createElement('script'), s=d.getElementsByTagName('script')[0];
+ g.async=true; g.src=u+'/matomo.js'; s.parentNode.insertBefore(g,s);
+ })();
+ </script>
+ <!-- End Matomo Code -->
</head>
<body class="topBarEnabled">
- <a href="https://github.com/apache/jackrabbit">
- <img style="position: absolute; top: 0; right: 0; border: 0; z-index: 10000;"
- src="https://s3.amazonaws.com/github/ribbons/forkme_right_red_aa0000.png"
- alt="Fork me on GitHub">
- </a>
+ <a class="github-fork-ribbon right-top" href="https://github.com/apache/jackrabbit" data-ribbon="Fork me on GitHub" title="Fork me on GitHub">Fork me on GitHub</a>
<header id="topbar" class="navbar navbar-fixed-top ">
<div class="navbar-inner">
<div class="container-fluid">
@@ -49,7 +47,7 @@
</a>
<ul class="nav">
<li class="dropdown">
- <a href="#" class="dropdown-toggle" data-toggle="dropdown">Apache Jackrabbit <b class="caret"></b></a>
+ <a class="dropdown-toggle" data-toggle="dropdown">Apache Jackrabbit <b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="index.html" title="Welcome">Welcome</a></li>
<li><a href="downloads.html" title="Downloads">Downloads</a></li>
@@ -60,14 +58,14 @@
</ul>
</li>
<li class="dropdown">
- <a href="#" class="dropdown-toggle" data-toggle="dropdown">Documentation <b class="caret"></b></a>
+ <a class="dropdown-toggle" data-toggle="dropdown">Documentation <b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="getting-started-with-apache-jackrabbit.html" title="Getting Started">Getting Started</a></li>
<li><a href="standalone-server.html" title="Standalone Server">Standalone Server</a></li>
<li><a href="jackrabbit-components.html" title="Jackrabbit Components">Jackrabbit Components</a></li>
<li><a href="first-hops.html" title="First Hops">First Hops</a></li>
<li><a href="jcr-api.html" title="JCR & API">JCR & API</a></li>
- <li><a href="jackrabbit-architecture.html" title="Jackrabbit Architecture">Jackrabbit Architecture</a></li>
+ <li><a title="Jackrabbit Architecture">Jackrabbit Architecture</a></li>
<li><a href="deployment-models.html" title="Deployment Models">Deployment Models</a></li>
<li><a href="jackrabbit-configuration.html" title="Jackrabbit Configuration">Jackrabbit Configuration</a></li>
<li><a href="node-types.html" title="Node Types">Node Types</a></li>
@@ -75,7 +73,7 @@
</ul>
</li>
<li class="dropdown">
- <a href="#" class="dropdown-toggle" data-toggle="dropdown">Development <b class="caret"></b></a>
+ <a class="dropdown-toggle" data-toggle="dropdown">Development <b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="jackrabbit-team.html" title="Jackrabbit Team">Jackrabbit Team</a></li>
<li><a href="jackrabbit-roadmap.html" title="Jackrabbit Roadmap">Jackrabbit Roadmap</a></li>
@@ -90,7 +88,7 @@
</ul>
</li>
<li class="dropdown">
- <a href="#" class="dropdown-toggle" data-toggle="dropdown">Apache Software Foundation <b class="caret"></b></a>
+ <a class="dropdown-toggle" data-toggle="dropdown">Apache Software Foundation <b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="https://www.apache.org/foundation/how-it-works.html" title="Introduction">Introduction</a></li>
<li><a href="https://www.apache.org/foundation/sponsorship.html" title="Sponsorship">Sponsorship</a></li>
@@ -105,7 +103,7 @@
<div class="container-fluid">
<header>
<div id="banner">
- <div class="pull-left"><div id="bannerLeft"><h2>Apache Jackrabbit Site</h2>
+ <div class="pull-left"><div id="bannerLeft"><h1>Apache Jackrabbit Site</h1>
</div>
</div>
<div class="pull-right"></div>
@@ -114,7 +112,7 @@
<div id="breadcrumbs">
<ul class="breadcrumb">
- <li id="publishDate">Last Published: 2022-05-12</li>
+ <li id="publishDate">Last Published: 2022-12-15</li>
</ul>
</div>
</header>
@@ -135,7 +133,7 @@
<li><a href="jackrabbit-components.html" title="Jackrabbit Components"><span class="none"></span>Jackrabbit Components</a></li>
<li><a href="first-hops.html" title="First Hops"><span class="none"></span>First Hops</a></li>
<li><a href="jcr-api.html" title="JCR & API"><span class="none"></span>JCR & API</a></li>
- <li class="active"><a href="#"><span class="none"></span>Jackrabbit Architecture</a></li>
+ <li class="active"><a><span class="none"></span>Jackrabbit Architecture</a></li>
<li><a href="deployment-models.html" title="Deployment Models"><span class="none"></span>Deployment Models</a></li>
<li><a href="jackrabbit-configuration.html" title="Jackrabbit Configuration"><span class="none"></span>Jackrabbit Configuration</a></li>
<li><a href="node-types.html" title="Node Types"><span class="none"></span>Node Types</a></li>
@@ -159,7 +157,6 @@
</ul>
</nav>
<div class="well sidebar-nav">
- <hr />
<div id="poweredBy">
<div class="clear"></div>
<div class="clear"></div>
@@ -194,12 +191,42 @@
<li><a href="index-readers.html">Index readers</a></li>
<li><a href="concurrency-control.html">Concurrency control</a></li>
</ul>
-<p>The general architecture of Jackrabbit can be described in three Layers: A Content Application Layer, an API Layer and a Content Repository Implementation Layer.</p>
+<p>The general architecture of Jackrabbit can be described in three Layers: A
+Content Application Layer, an API Layer and a Content Repository
+Implementation Layer.</p>
<p><img src="jackrabbit-architecture.png" alt="Jackrabbit Architecture Overview" /></p><section>
<h2><a name="Content_Applications"></a>Content Applications</h2>
-<p>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.</p>
-<p>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).</p>
-<p>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”.</p></section><section>
+<p>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.</p>
+<p>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).</p>
+<p>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”.</p></section><section>
<h2><a name="Content_Repository_API"></a>Content Repository API</h2>
<p>The Content Repository API Layer is split into two major sections.</p>
<ul>
@@ -210,16 +237,28 @@
</li>
<li>
-<p>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</p>
+<p>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</p>
</li>
</ul>
-<p>There are only very few (mostly administrational) applications which make use of the non-JSR-170 APIs provided by Jackrabbit.</p>
-<p>The boxes in the architecture chart do not symbolize package names or class names directly but mostly semantically grouped blocks of functionality.</p></section><section>
+<p>There are only very few (mostly administrational) applications which make
+use of the non-JSR-170 APIs provided by Jackrabbit.</p>
+<p>The boxes in the architecture chart do not symbolize package names or class
+names directly but mostly semantically grouped blocks of functionality.</p></section><section>
<h2><a name="Content_Repository_Implementation"></a>Content Repository Implementation</h2>
-<p>The content Repository Implementation portion of the architecture chart reflects the major building blocks of the jackrabbit content repository implementation.</p>
-<p>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.</p>
-<p>There are three scopes in a content repository: A repository scope, a workspace scope and a session scope.</p>
-<p>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.</p>
+<p>The content Repository Implementation portion of the architecture chart
+reflects the major building blocks of the jackrabbit content repository
+implementation.</p>
+<p>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.</p>
+<p>There are three scopes in a content repository: A repository scope, a
+workspace scope and a session scope.</p>
+<p>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.</p>
<ul>
<li>Repository</li>
@@ -239,7 +278,8 @@
<li>ItemId, PropertyId, NodeId</li>
<li>ItemManager</li>
</ul>
-<p>This is not a complete list but includes some of the most important component of the content repository implementation.</p></section>
+<p>This is not a complete list but includes some of the most important
+component of the content repository implementation.</p></section>
</main>
</div>
</div>
@@ -251,10 +291,12 @@
<a href="https://www.apache.org/">The Apache Software Foundation</a> | <a href="https://privacy.apache.org/policies/privacy-policy-public.html">Privacy Policy</a>
</p>
</div>
- <div id="ohloh" class="pull-right">
- <script src="https://www.ohloh.net/p/jackrabbit/widgets/project_users_logo.js"></script>
- </div>
- </div>
+ </div>
</footer>
+<script>
+ if(anchors) {
+ anchors.add();
+ }
+</script>
</body>
</html>
\ No newline at end of file
Modified: jackrabbit/site/live/jcr/jackrabbit-components.html
URL: http://svn.apache.org/viewvc/jackrabbit/site/live/jcr/jackrabbit-components.html?rev=1906010&r1=1906009&r2=1906010&view=diff
==============================================================================
--- jackrabbit/site/live/jcr/jackrabbit-components.html (original)
+++ jackrabbit/site/live/jcr/jackrabbit-components.html Thu Dec 15 09:54:26 2022
@@ -1,42 +1,40 @@
<!DOCTYPE html>
+
+
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.9.2 from src\site\markdown/jackrabbit-components.md at 2022-05-12
- | Rendered using Apache Maven Fluido Skin 1.9
+ | Generated by Apache Maven Doxia Site Renderer 1.11.1 from src/site/markdown/jackrabbit-components.md at 2022-12-15
+ | Rendered using Apache Maven Fluido Skin 1.11.1
-->
<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 1.9.2" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 1.11.1" />
<title>Apache Jackrabbit – Jackrabbit Components</title>
- <link rel="stylesheet" href="./css/apache-maven-fluido-1.9.min.css" />
+ <link rel="stylesheet" href="./css/apache-maven-fluido-1.11.1.min.css" />
<link rel="stylesheet" href="./css/site.css" />
<link rel="stylesheet" href="./css/print.css" media="print" />
- <script src="./js/apache-maven-fluido-1.9.min.js"></script>
-<!-- Matomo -->
-<script>
- var _paq = window._paq = window._paq || [];
- /* tracker methods like "setCustomDimension" should be called before "trackPageView" */
- /* We explicitly disable cookie tracking to avoid privacy issues */
- _paq.push(['disableCookies']);
- _paq.push(['trackPageView']);
- _paq.push(['enableLinkTracking']);
- (function() {
- var u="https://matomo.privacy.apache.org/";
- _paq.push(['setTrackerUrl', u+'matomo.php']);
- _paq.push(['setSiteId', '4']);
- var d=document, g=d.createElement('script'), s=d.getElementsByTagName('script')[0];
- g.async=true; g.src=u+'matomo.js'; s.parentNode.insertBefore(g,s);
- })();
-</script>
-<!-- End Matomo Code -->
+ <script src="./js/apache-maven-fluido-1.11.1.min.js"></script>
+
+ <!-- Matomo -->
+ <script>
+ var _paq = window._paq = window._paq || [];
+ _paq.push(['disableCookies']);
+ _paq.push(['trackPageView']);
+ _paq.push(['enableLinkTracking']);
+
+ (function() {
+ var u="https://analytics.apache.org";
+ _paq.push(['setTrackerUrl', u+'/matomo.php']);
+ _paq.push(['setSiteId', '4']);
+ var d=document, g=d.createElement('script'), s=d.getElementsByTagName('script')[0];
+ g.async=true; g.src=u+'/matomo.js'; s.parentNode.insertBefore(g,s);
+ })();
+ </script>
+ <!-- End Matomo Code -->
</head>
<body class="topBarEnabled">
- <a href="https://github.com/apache/jackrabbit">
- <img style="position: absolute; top: 0; right: 0; border: 0; z-index: 10000;"
- src="https://s3.amazonaws.com/github/ribbons/forkme_right_red_aa0000.png"
- alt="Fork me on GitHub">
- </a>
+ <a class="github-fork-ribbon right-top" href="https://github.com/apache/jackrabbit" data-ribbon="Fork me on GitHub" title="Fork me on GitHub">Fork me on GitHub</a>
<header id="topbar" class="navbar navbar-fixed-top ">
<div class="navbar-inner">
<div class="container-fluid">
@@ -49,7 +47,7 @@
</a>
<ul class="nav">
<li class="dropdown">
- <a href="#" class="dropdown-toggle" data-toggle="dropdown">Apache Jackrabbit <b class="caret"></b></a>
+ <a class="dropdown-toggle" data-toggle="dropdown">Apache Jackrabbit <b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="index.html" title="Welcome">Welcome</a></li>
<li><a href="downloads.html" title="Downloads">Downloads</a></li>
@@ -60,11 +58,11 @@
</ul>
</li>
<li class="dropdown">
- <a href="#" class="dropdown-toggle" data-toggle="dropdown">Documentation <b class="caret"></b></a>
+ <a class="dropdown-toggle" data-toggle="dropdown">Documentation <b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="getting-started-with-apache-jackrabbit.html" title="Getting Started">Getting Started</a></li>
<li><a href="standalone-server.html" title="Standalone Server">Standalone Server</a></li>
- <li><a href="jackrabbit-components.html" title="Jackrabbit Components">Jackrabbit Components</a></li>
+ <li><a title="Jackrabbit Components">Jackrabbit Components</a></li>
<li><a href="first-hops.html" title="First Hops">First Hops</a></li>
<li><a href="jcr-api.html" title="JCR & API">JCR & API</a></li>
<li><a href="jackrabbit-architecture.html" title="Jackrabbit Architecture">Jackrabbit Architecture</a></li>
@@ -75,7 +73,7 @@
</ul>
</li>
<li class="dropdown">
- <a href="#" class="dropdown-toggle" data-toggle="dropdown">Development <b class="caret"></b></a>
+ <a class="dropdown-toggle" data-toggle="dropdown">Development <b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="jackrabbit-team.html" title="Jackrabbit Team">Jackrabbit Team</a></li>
<li><a href="jackrabbit-roadmap.html" title="Jackrabbit Roadmap">Jackrabbit Roadmap</a></li>
@@ -90,7 +88,7 @@
</ul>
</li>
<li class="dropdown">
- <a href="#" class="dropdown-toggle" data-toggle="dropdown">Apache Software Foundation <b class="caret"></b></a>
+ <a class="dropdown-toggle" data-toggle="dropdown">Apache Software Foundation <b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="https://www.apache.org/foundation/how-it-works.html" title="Introduction">Introduction</a></li>
<li><a href="https://www.apache.org/foundation/sponsorship.html" title="Sponsorship">Sponsorship</a></li>
@@ -105,7 +103,7 @@
<div class="container-fluid">
<header>
<div id="banner">
- <div class="pull-left"><div id="bannerLeft"><h2>Apache Jackrabbit Site</h2>
+ <div class="pull-left"><div id="bannerLeft"><h1>Apache Jackrabbit Site</h1>
</div>
</div>
<div class="pull-right"></div>
@@ -114,7 +112,7 @@
<div id="breadcrumbs">
<ul class="breadcrumb">
- <li id="publishDate">Last Published: 2022-05-12</li>
+ <li id="publishDate">Last Published: 2022-12-15</li>
</ul>
</div>
</header>
@@ -132,7 +130,7 @@
<li class="nav-header">Documentation</li>
<li><a href="getting-started-with-apache-jackrabbit.html" title="Getting Started"><span class="none"></span>Getting Started</a></li>
<li><a href="standalone-server.html" title="Standalone Server"><span class="none"></span>Standalone Server</a></li>
- <li class="active"><a href="#"><span class="none"></span>Jackrabbit Components</a></li>
+ <li class="active"><a><span class="none"></span>Jackrabbit Components</a></li>
<li><a href="first-hops.html" title="First Hops"><span class="none"></span>First Hops</a></li>
<li><a href="jcr-api.html" title="JCR & API"><span class="none"></span>JCR & API</a></li>
<li><a href="jackrabbit-architecture.html" title="Jackrabbit Architecture"><span class="none"></span>Jackrabbit Architecture</a></li>
@@ -159,7 +157,6 @@
</ul>
</nav>
<div class="well sidebar-nav">
- <hr />
<div id="poweredBy">
<div class="clear"></div>
<div class="clear"></div>
@@ -214,7 +211,9 @@
<li><a class="externalLink" href="https://jackrabbit.apache.org/filevault/">Jackrabbit FileVault</a></li>
<li><a class="externalLink" href="https://jackrabbit.apache.org/filevault-package-maven-plugin/">Jackrabbit FileVault Package Maven Plugin</a></li>
</ul>
-<p>In addition there are a number of contributed components in the <i>sandbox</i> folder of the Jackrabbit project. These components are not yet considered stable enough to be included in the official Apache Jackrabbit releases.</p>
+<p>In addition there are a number of contributed components in the <i>sandbox</i>
+folder of the Jackrabbit project. These components are not yet considered
+stable enough to be included in the official Apache Jackrabbit releases.</p>
</main>
</div>
</div>
@@ -226,10 +225,12 @@
<a href="https://www.apache.org/">The Apache Software Foundation</a> | <a href="https://privacy.apache.org/policies/privacy-policy-public.html">Privacy Policy</a>
</p>
</div>
- <div id="ohloh" class="pull-right">
- <script src="https://www.ohloh.net/p/jackrabbit/widgets/project_users_logo.js"></script>
- </div>
- </div>
+ </div>
</footer>
+<script>
+ if(anchors) {
+ anchors.add();
+ }
+</script>
</body>
</html>
\ No newline at end of file
Modified: jackrabbit/site/live/jcr/jackrabbit-configuration.html
URL: http://svn.apache.org/viewvc/jackrabbit/site/live/jcr/jackrabbit-configuration.html?rev=1906010&r1=1906009&r2=1906010&view=diff
==============================================================================
--- jackrabbit/site/live/jcr/jackrabbit-configuration.html (original)
+++ jackrabbit/site/live/jcr/jackrabbit-configuration.html Thu Dec 15 09:54:26 2022
@@ -1,42 +1,40 @@
<!DOCTYPE html>
+
+
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.9.2 from src\site\markdown/jackrabbit-configuration.md at 2022-05-12
- | Rendered using Apache Maven Fluido Skin 1.9
+ | Generated by Apache Maven Doxia Site Renderer 1.11.1 from src/site/markdown/jackrabbit-configuration.md at 2022-12-15
+ | Rendered using Apache Maven Fluido Skin 1.11.1
-->
<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 1.9.2" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 1.11.1" />
<title>Apache Jackrabbit – Jackrabbit Configuration</title>
- <link rel="stylesheet" href="./css/apache-maven-fluido-1.9.min.css" />
+ <link rel="stylesheet" href="./css/apache-maven-fluido-1.11.1.min.css" />
<link rel="stylesheet" href="./css/site.css" />
<link rel="stylesheet" href="./css/print.css" media="print" />
- <script src="./js/apache-maven-fluido-1.9.min.js"></script>
-<!-- Matomo -->
-<script>
- var _paq = window._paq = window._paq || [];
- /* tracker methods like "setCustomDimension" should be called before "trackPageView" */
- /* We explicitly disable cookie tracking to avoid privacy issues */
- _paq.push(['disableCookies']);
- _paq.push(['trackPageView']);
- _paq.push(['enableLinkTracking']);
- (function() {
- var u="https://matomo.privacy.apache.org/";
- _paq.push(['setTrackerUrl', u+'matomo.php']);
- _paq.push(['setSiteId', '4']);
- var d=document, g=d.createElement('script'), s=d.getElementsByTagName('script')[0];
- g.async=true; g.src=u+'matomo.js'; s.parentNode.insertBefore(g,s);
- })();
-</script>
-<!-- End Matomo Code -->
+ <script src="./js/apache-maven-fluido-1.11.1.min.js"></script>
+
+ <!-- Matomo -->
+ <script>
+ var _paq = window._paq = window._paq || [];
+ _paq.push(['disableCookies']);
+ _paq.push(['trackPageView']);
+ _paq.push(['enableLinkTracking']);
+
+ (function() {
+ var u="https://analytics.apache.org";
+ _paq.push(['setTrackerUrl', u+'/matomo.php']);
+ _paq.push(['setSiteId', '4']);
+ var d=document, g=d.createElement('script'), s=d.getElementsByTagName('script')[0];
+ g.async=true; g.src=u+'/matomo.js'; s.parentNode.insertBefore(g,s);
+ })();
+ </script>
+ <!-- End Matomo Code -->
</head>
<body class="topBarEnabled">
- <a href="https://github.com/apache/jackrabbit">
- <img style="position: absolute; top: 0; right: 0; border: 0; z-index: 10000;"
- src="https://s3.amazonaws.com/github/ribbons/forkme_right_red_aa0000.png"
- alt="Fork me on GitHub">
- </a>
+ <a class="github-fork-ribbon right-top" href="https://github.com/apache/jackrabbit" data-ribbon="Fork me on GitHub" title="Fork me on GitHub">Fork me on GitHub</a>
<header id="topbar" class="navbar navbar-fixed-top ">
<div class="navbar-inner">
<div class="container-fluid">
@@ -49,7 +47,7 @@
</a>
<ul class="nav">
<li class="dropdown">
- <a href="#" class="dropdown-toggle" data-toggle="dropdown">Apache Jackrabbit <b class="caret"></b></a>
+ <a class="dropdown-toggle" data-toggle="dropdown">Apache Jackrabbit <b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="index.html" title="Welcome">Welcome</a></li>
<li><a href="downloads.html" title="Downloads">Downloads</a></li>
@@ -60,7 +58,7 @@
</ul>
</li>
<li class="dropdown">
- <a href="#" class="dropdown-toggle" data-toggle="dropdown">Documentation <b class="caret"></b></a>
+ <a class="dropdown-toggle" data-toggle="dropdown">Documentation <b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="getting-started-with-apache-jackrabbit.html" title="Getting Started">Getting Started</a></li>
<li><a href="standalone-server.html" title="Standalone Server">Standalone Server</a></li>
@@ -69,13 +67,13 @@
<li><a href="jcr-api.html" title="JCR & API">JCR & API</a></li>
<li><a href="jackrabbit-architecture.html" title="Jackrabbit Architecture">Jackrabbit Architecture</a></li>
<li><a href="deployment-models.html" title="Deployment Models">Deployment Models</a></li>
- <li><a href="jackrabbit-configuration.html" title="Jackrabbit Configuration">Jackrabbit Configuration</a></li>
+ <li><a title="Jackrabbit Configuration">Jackrabbit Configuration</a></li>
<li><a href="node-types.html" title="Node Types">Node Types</a></li>
<li><a href="object-content-mapping.html" title="Object Content Mapping">Object Content Mapping</a></li>
</ul>
</li>
<li class="dropdown">
- <a href="#" class="dropdown-toggle" data-toggle="dropdown">Development <b class="caret"></b></a>
+ <a class="dropdown-toggle" data-toggle="dropdown">Development <b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="jackrabbit-team.html" title="Jackrabbit Team">Jackrabbit Team</a></li>
<li><a href="jackrabbit-roadmap.html" title="Jackrabbit Roadmap">Jackrabbit Roadmap</a></li>
@@ -90,7 +88,7 @@
</ul>
</li>
<li class="dropdown">
- <a href="#" class="dropdown-toggle" data-toggle="dropdown">Apache Software Foundation <b class="caret"></b></a>
+ <a class="dropdown-toggle" data-toggle="dropdown">Apache Software Foundation <b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="https://www.apache.org/foundation/how-it-works.html" title="Introduction">Introduction</a></li>
<li><a href="https://www.apache.org/foundation/sponsorship.html" title="Sponsorship">Sponsorship</a></li>
@@ -105,7 +103,7 @@
<div class="container-fluid">
<header>
<div id="banner">
- <div class="pull-left"><div id="bannerLeft"><h2>Apache Jackrabbit Site</h2>
+ <div class="pull-left"><div id="bannerLeft"><h1>Apache Jackrabbit Site</h1>
</div>
</div>
<div class="pull-right"></div>
@@ -114,7 +112,7 @@
<div id="breadcrumbs">
<ul class="breadcrumb">
- <li id="publishDate">Last Published: 2022-05-12</li>
+ <li id="publishDate">Last Published: 2022-12-15</li>
</ul>
</div>
</header>
@@ -137,7 +135,7 @@
<li><a href="jcr-api.html" title="JCR & API"><span class="none"></span>JCR & API</a></li>
<li><a href="jackrabbit-architecture.html" title="Jackrabbit Architecture"><span class="none"></span>Jackrabbit Architecture</a></li>
<li><a href="deployment-models.html" title="Deployment Models"><span class="none"></span>Deployment Models</a></li>
- <li class="active"><a href="#"><span class="none"></span>Jackrabbit Configuration</a></li>
+ <li class="active"><a><span class="none"></span>Jackrabbit Configuration</a></li>
<li><a href="node-types.html" title="Node Types"><span class="none"></span>Node Types</a></li>
<li><a href="object-content-mapping.html" title="Object Content Mapping"><span class="none"></span>Object Content Mapping</a></li>
<li class="nav-header">Development</li>
@@ -159,7 +157,6 @@
</ul>
</nav>
<div class="well sidebar-nav">
- <hr />
<div id="poweredBy">
<div class="clear"></div>
<div class="clear"></div>
@@ -186,24 +183,57 @@
limitations under the License.
-->
<h1>Jackrabbit Configuration</h1>
-<p>Apache Jackrabbit needs two pieces of information to set up a runtime content repository instance:</p>
+<p>Apache Jackrabbit needs two pieces of information to set up a runtime
+content repository instance:</p>
<ul>
<li>
<p><b>Repository home directory</b><br />
-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.</p>
+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.</p>
</li>
<li>
<p><b>Repository configuration file</b><br />
-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.</p>
+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.</p>
</li>
</ul>
-<p>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.</p>
-<p>For each workspace that was created, there will also be a <code>workspace.xml</code> 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 <code>createWorkspace()</code> method of the Jackrabbit API, the <code>workspace.xml</code> is just a copy of the <a href="#workspace-configuration">Workspace</a> element inside <code>repository.xml</code>. 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 <a href="#persistence-configuration">persistence manager</a> you will also have to setup a database and configure the access to it).</p><section>
+<p>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.</p>
+<p>For each workspace that was created, there will also be a <code>workspace.xml</code>
+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 <code>createWorkspace()</code>
+method of the Jackrabbit API, the <code>workspace.xml</code> is just a copy of the <a href="#workspace-configuration">Workspace</a>
+element inside <code>repository.xml</code>. 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 <a href="#persistence-configuration">persistence manager</a>
+you will also have to setup a database and configure the access to it).</p><section>
<h2><a name="Repository_configuration"></a>Repository configuration</h2>
-<p>The repository configuration file, typically called <code>repository.xml</code>, 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.</p>
+<p>The repository configuration file, typically called <code>repository.xml</code>,
+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.</p>
<ul>
<li><a class="externalLink" href="http://jackrabbit.apache.org/dtd/repository-1.5.dtd">-//The Apache Software Foundation//DTD Jackrabbit 1.5//EN</a></li>
@@ -211,11 +241,17 @@ The filesystem path of the repository co
<li><a class="externalLink" href="http://jackrabbit.apache.org/dtd/repository-1.2.dtd">-//The Apache Software Foundation//DTD Jackrabbit 1.2//EN</a></li>
<li><a class="externalLink" href="http://jackrabbit.apache.org/dtd/repository-1.0.dtd">-//The Apache Software Foundation//DTD Jackrabbit 1.0//EN</a></li>
</ul>
-<p>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.</p>
-<p>The top-level structure of the repository configuration file is shown below. The <code><!DOCTYPE></code> 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.</p>
+<p>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.</p>
+<p>The top-level structure of the repository configuration file is shown
+below. The <code><!DOCTYPE></code> 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.</p>
-<div class="source">
-<div class="source"><pre class="prettyprint linenums"><!DOCTYPE Repository
+<div class="source"><pre class="prettyprint linenums"><code><!DOCTYPE Repository
PUBLIC "-//The Apache Software Foundation//DTD Jackrabbit 1.5//EN"
"http://jackrabbit.apache.org/dtd/repository-1.5.dtd">
<Repository>
@@ -228,9 +264,9 @@ The filesystem path of the repository co
<Cluster .../> <!-- optional, available since 1.2 -->
<DataStore .../> <!-- optional, available since 1.4 -->
</Repository>
-</pre></div></div>
-
-<p>Starting with Jackrabbit 1.5, the order of the configuration elements below <code><Repository/></code> is now fixed.</p>
+</code></pre></div>
+<p>Starting with Jackrabbit 1.5, the order of the configuration elements below
+<code><Repository/></code> is now fixed.</p>
<p>The repository configuration elements are:</p>
<ul>
@@ -246,77 +282,119 @@ The filesystem path of the repository co
<p>See the Jackrabbit 1.5 <a href="repository.xml">default configuration</a> , for an example repository configuration file.</p>
<blockquote>
-<p>It is a good idea to place the <code>repository.xml</code> file <i>inside</i> the repository home directory. This keeps your repository and its configuration nicely contained within a single directory tree.</p>
+<p>It is a good idea to place the <code>repository.xml</code> file <i>inside</i> the
+repository home directory. This keeps your repository and its configuration
+nicely contained within a single directory tree.</p>
</blockquote><section>
<h3><a name="Bean_configuration_elements"></a>Bean configuration elements</h3>
-<p>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.</p>
+<p>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.</p>
-<div class="source">
-<div class="source"><pre class="prettyprint linenums"><ConfigurationElement class="fully.qualified.ClassName">
+<div class="source"><pre class="prettyprint linenums"><code><ConfigurationElement class="fully.qualified.ClassName">
<param name="property1" value="...">
<param name="property2" value="...">
<ConfigurationElement>
-</pre></div></div>
-</section><section>
+</code></pre></div></section><section>
<h3><a name="Configuration_variables"></a>Configuration variables</h3>
-<p>Jackrabbit supports configuration variables of the form <code>${name}</code>. These variables can be used to avoid hardcoding specific options in the configuration files. The following variables are available in all Jackrabbit versions:</p>
+<p>Jackrabbit supports configuration variables of the form <code>${name}</code>. These
+variables can be used to avoid hardcoding specific options in the
+configuration files. The following variables are available in all
+Jackrabbit versions:</p>
<ul>
<li><code>${rep.home}</code>: Repository home directory.</li>
<li><code>${wsp.name}</code>: Workspace name. Only available in workspace configuration.</li>
<li><code>${wsp.home}</code>: Workspace home directory. Only available in workspace configuration.</li>
</ul>
-<p>Since Jackrabbit 1.4 (see <a class="externalLink" href="https://issues.apache.org/jira/browse/JCR-1304">JCR-1304</a>) it has been possible to use system properties or any application-specific settings as configuration variables.</p></section></section><section>
-<h2><a name="Security_configuration"></a><a name="security-configuration"></a> Security configuration</h2>
-<p>The security configuration element is used to specify authentication and authorization settings for the repository. The structure of the security configuration element is:</p>
+<p>Since Jackrabbit 1.4 (see <a class="externalLink" href="https://issues.apache.org/jira/browse/JCR-1304">JCR-1304</a>)
+it has been possible to use system properties or any application-specific
+settings as configuration variables.</p></section></section><section>
+<h2><a name="Security_configuration"></a><a name="security-configuration"></a>
+Security configuration</h2>
+<p>The security configuration element is used to specify authentication and
+authorization settings for the repository. The structure of the security
+configuration element is:</p>
-<div class="source">
-<div class="source"><pre class="prettyprint linenums"><Security appName="Jackrabbit">
+<div class="source"><pre class="prettyprint linenums"><code><Security appName="Jackrabbit">
<SecurityManager .../> <!-- optional, available since 1.5 -->
<AccessManager .../> <!-- mandatory until 1.4, optional since 1.5 -->
<LoginModule .../> <!-- optional -->
</Security>
-</pre></div></div>
-
-<p>By default Jackrabbit uses the <a class="externalLink" href="http://java.sun.com/j2se/1.4.2/docs/guide/security/jaas/JAASRefGuide.html">Java Authentication and Authorization Service</a> (JAAS) to authenticate users who try to access the repository. The <code>appName</code> parameter in the <code><Security/></code> element is used as the JAAS application name of the repository.</p>
-<p>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 <a class="externalLink" href="http://java.sun.com/j2se/1.4.2/docs/api/javax/security/auth/spi/LoginModule.html">LoginModule</a> that is then used for authenticating repository users. The default <a class="externalLink" href="http://jackrabbit.apache.org/api/1.5/org/apache/jackrabbit/core/security/SimpleLoginModule.html">SimpleLoginModule</a> class included in Jackrabbit implements a trivially simple authentication mechanism that accepts any username and any password as valid authentication credentials.</p>
-<p>Once a user has been authenticated, Jackrabbit will use the configured <a class="externalLink" href="http://jackrabbit.apache.org/api/1.5/org/apache/jackrabbit/core/security/AccessManager.html">AccessManager</a> 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.</p>
-<p>The slightly more advanced <a class="externalLink" href="http://jackrabbit.apache.org/api/1.5/org/apache/jackrabbit/core/security/SimpleJBossAccessManager.html">SimpleJBossAccessManager</a> class was added in Jackrabbit 1.3 (see <a class="externalLink" href="https://issues.apache.org/jira/browse/JCR-650">JCR-650</a>). This class is designed for use with the <a class="externalLink" href="http://www.jboss.org/jbossas/">JBoss Application Server</a>, where it maps JBoss roles to Jackrabbit permissions.</p></section><section>
-<h2><a name="Workspace_configuration"></a><a name="workspace-configuration"></a> Workspace configuration</h2>
-<p>A Jackrabbit repository contains one or more workspaces that are each configured in a separate <code>workspace.xml</code> configuration file. The <code>Workspaces</code> 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 <code>workspace.xml</code> file of a new workspace unless more specific configuration is given when the workspace is created. See the <code>createWorkspace</code> methods in the <a class="externalLink" href="http://jackrabbit.apache.org/api/1.5/org/apache/jackrabbit/api/JackrabbitWorkspace.html">JackrabbitWorkspace</a> interface for more details on workspace creating workspaces.</p>
+</code></pre></div>
+<p>By default Jackrabbit uses the <a class="externalLink" href="http://java.sun.com/j2se/1.4.2/docs/guide/security/jaas/JAASRefGuide.html">Java Authentication and Authorization Service</a>
+(JAAS) to authenticate users who try to access the repository. The
+<code>appName</code> parameter in the <code><Security/></code> element is used as the JAAS
+application name of the repository.</p>
+<p>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 <a class="externalLink" href="http://java.sun.com/j2se/1.4.2/docs/api/javax/security/auth/spi/LoginModule.html">LoginModule</a>
+that is then used for authenticating repository users. The default <a class="externalLink" href="http://jackrabbit.apache.org/api/1.5/org/apache/jackrabbit/core/security/SimpleLoginModule.html">SimpleLoginModule</a>
+class included in Jackrabbit implements a trivially simple authentication
+mechanism that accepts any username and any password as valid
+authentication credentials.</p>
+<p>Once a user has been authenticated, Jackrabbit will use the configured <a class="externalLink" href="http://jackrabbit.apache.org/api/1.5/org/apache/jackrabbit/core/security/AccessManager.html">AccessManager</a>
+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.</p>
+<p>The slightly more advanced <a class="externalLink" href="http://jackrabbit.apache.org/api/1.5/org/apache/jackrabbit/core/security/SimpleJBossAccessManager.html">SimpleJBossAccessManager</a>
+class was added in Jackrabbit 1.3 (see <a class="externalLink" href="https://issues.apache.org/jira/browse/JCR-650">JCR-650</a>).
+This class is designed for use with the <a class="externalLink" href="http://www.jboss.org/jbossas/">JBoss Application Server</a>,
+where it maps JBoss roles to Jackrabbit permissions.</p></section><section>
+<h2><a name="Workspace_configuration"></a><a name="workspace-configuration"></a>
+Workspace configuration</h2>
+<p>A Jackrabbit repository contains one or more workspaces that are each
+configured in a separate <code>workspace.xml</code> configuration file. The
+<code>Workspaces</code> 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
+<code>workspace.xml</code> file of a new workspace unless more specific
+configuration is given when the workspace is created. See the
+<code>createWorkspace</code> methods in the <a class="externalLink" href="http://jackrabbit.apache.org/api/1.5/org/apache/jackrabbit/api/JackrabbitWorkspace.html">JackrabbitWorkspace</a>
+interface for more details on workspace creating workspaces.</p>
<p>The workspace settings in the repository configuration file are:</p>
-<div class="source">
-<div class="source"><pre class="prettyprint linenums"><Workspaces rootPath="${rep.home}/workspaces"
+<div class="source"><pre class="prettyprint linenums"><code><Workspaces rootPath="${rep.home}/workspaces"
defaultWorkspace="default"
configRootPath="..." <!-- optional -->
maxIdleTime="..."/> <!-- optional -->
<Workspace .../> <!-- default workspace configuration template -->
-</pre></div></div>
-
+</code></pre></div>
<p>The following global workspace configuration options are specified in the <code>Workspaces</code> element:</p>
<ul>
<li><code>rootPath</code>:<br />
-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 <code>${wsp.path}</code> variable.</li>
+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 <code>${wsp.path}</code> variable.</li>
<li><code>defaultWorkspace</code>:<br />
-Name of the default workspace. This workspace is automatically created when the repository is first started.</li>
+Name of the default workspace. This workspace is
+automatically created when the repository is first started.</li>
<li><code>configRootPath</code>:<br />
-By default the configuration of each workspace is stored in a <i>workspace.xml</i> file within the workspace directory within the <code>rootPath</code> 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.</li>
+By default the configuration of each workspace is
+stored in a <i>workspace.xml</i> file within the workspace directory within
+the <code>rootPath</code> 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.</li>
<li><code>maxIdleTime</code>:<br />
-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.</li>
+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.</li>
</ul>
-<p>The workspace configuration template and all <i>workspace.xml</i> configuration files have the following structure:</p>
+<p>The workspace configuration template and all <i>workspace.xml</i>
+configuration files have the following structure:</p>
-<div class="source">
-<div class="source"><pre class="prettyprint linenums"><Workspace name="${wsp.name}">
+<div class="source"><pre class="prettyprint linenums"><code><Workspace name="${wsp.name}">
<FileSystem .../>
<PersistenceManager .../>
<SearchIndex .../> <!-- optional -->
<ISMLocking .../> <!-- optional, available since 1.4 -->
</Workspace>
-</pre></div></div>
-
+</code></pre></div>
<p>The workspace configuration elements are:</p>
<ul>
@@ -327,20 +405,31 @@ By default Jackrabbit only releases reso
</ul>
<blockquote>
-<p>To modify the configuration of an existing workspace, you need to change the <code>workspace.xml</code> file of that workspace. Changing the <code><Workspace/></code> element in the repository configuration file will not affect existing workspaces.</p>
+<p>To modify the configuration of an existing workspace, you need to change
+the <code>workspace.xml</code> file of that workspace. Changing the <code><Workspace/></code>
+element in the repository configuration file will not affect existing
+workspaces.</p>
</blockquote></section><section>
-<h2><a name="Versioning_configuration"></a><a name="versioning-configuration"></a> Versioning configuration</h2>
-<p>The version histories of all versionable nodes are stored in a repository-wide version store configured in the <code>Versioning</code> 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 <code>${wsp.name}</code> or <code>${wsp.path}</code> variables for the versioning configuration. Instead the native file system path of the version store is explicitly specified in the configuration.</p>
+<h2><a name="Versioning_configuration"></a><a name="versioning-configuration"></a>
+Versioning configuration</h2>
+<p>The version histories of all versionable nodes are stored in a
+repository-wide version store configured in the <code>Versioning</code> 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 <code>${wsp.name}</code> or <code>${wsp.path}</code>
+variables for the versioning configuration. Instead the native file system
+path of the version store is explicitly specified in the configuration.</p>
<p>The structure of the versioning configuration is:</p>
-<div class="source">
-<div class="source"><pre class="prettyprint linenums"><Versioning rootPath="${rep.home}/version">
+<div class="source"><pre class="prettyprint linenums"><code><Versioning rootPath="${rep.home}/version">
<FileSystem .../>
<PersistenceManager .../>
<ISMLocking .../> <!-- optional, available since 1.4 -->
</Versioning>
-</pre></div></div>
-
+</code></pre></div>
<p>The versioning configuration elements are:</p>
<ul>
@@ -348,33 +437,70 @@ By default Jackrabbit only releases reso
<li><a href="#persistence-configuration">PersistenceManager</a>: Persistence configuration for the version store.</li>
<li><a href="#item-state-locking-configuration">ISMLocking</a>: Locking configuration for concurrent access to workspace content.</li>
</ul></section><section>
-<h2><a name="Search_configuration"></a><a name="search-configuration"></a> Search configuration</h2>
+<h2><a name="Search_configuration"></a><a name="search-configuration"></a>
+Search configuration</h2>
<p>See the <a class="externalLink" href="http://jackrabbit.apache.org/archive/wiki/JCR/Search_115513504.html">Search</a> page on the Jackrabbit wiki.</p></section><section>
-<h2><a name="Persistence_configuration"></a><a name="persistence-configuration"></a> Persistence configuration</h2>
-<p>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).</p>
-<p>For large binary properties there is the option to use the <a href="#data-store-configuration">DataStore</a> instead of the Persistence Manager.</p>
-<p>For more detailed information and an overview of available PMs, see the <a class="externalLink" href="http://jackrabbit.apache.org/archive/wiki/JCR/PersistenceManagerFAQ_115513487.html">PersistenceManagerFAQ</a> page on the Jackrabbit wiki.</p>
+<h2><a name="Persistence_configuration"></a><a name="persistence-configuration"></a>
+Persistence configuration</h2>
+<p>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).</p>
+<p>For large binary properties there is the option to use the <a href="#data-store-configuration">DataStore</a>
+instead of the Persistence Manager.</p>
+<p>For more detailed information and an overview of available PMs, see the <a class="externalLink" href="http://jackrabbit.apache.org/archive/wiki/JCR/PersistenceManagerFAQ_115513487.html">PersistenceManagerFAQ</a>
+page on the Jackrabbit wiki.</p>
<blockquote>
-<p>If you use a database persistence manager, the configured database connection <i>must not</i> 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.</p>
+<p>If you use a database persistence manager, the configured database
+connection <i>must not</i> 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.</p>
</blockquote></section><section>
-<h2><a name="File_system_configuration"></a><a name="filesystem-configuration"></a> File system configuration</h2>
-<p>Early versions on Jackrabbit were designed to abstract their persistence mechanism using a virtual file system layer defined in the <a class="externalLink" href="http://jackrabbit.apache.org/api/1.5/org/apache/jackrabbit/core/fs/FileSystem.html">FileSystem</a> 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.</p>
-<p>A virtual file system is configured in a <code><FileSystem/></code> bean configuration element. See the main file system implementations <a class="externalLink" href="http://jackrabbit.apache.org/api/1.5/org/apache/jackrabbit/core/fs/local/LocalFileSystem.html">LocalFileSystem</a>, <a class="externalLink" href="http://jackrabbit.apache.org/api/1.5/org/apache/jackrabbit/core/fs/db/DatabaseFileSystem.html">DatabaseFileSystem</a> (including subclasses), and <a class="externalLink" href="http://jackrabbit.apache.org/api/1.5/org/apache/jackrabbit/core/fs/mem/MemoryFileSystem.html">MemoryFileSystem</a> for the available options. The recommended alternative is to use the <code>LocalFileSystem</code> implementation that simply maps abstract file system accesses to the specified directory within the native file system.</p></section><section>
-<h2><a name="Cluster_configuration"></a><a name="cluster-configuration"></a> Cluster configuration</h2>
+<h2><a name="File_system_configuration"></a><a name="filesystem-configuration"></a>
+File system configuration</h2>
+<p>Early versions on Jackrabbit were designed to abstract their persistence
+mechanism using a virtual file system layer defined in the <a class="externalLink" href="http://jackrabbit.apache.org/api/1.5/org/apache/jackrabbit/core/fs/FileSystem.html">FileSystem</a>
+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.</p>
+<p>A virtual file system is configured in a <code><FileSystem/></code> bean
+configuration element. See the main file system implementations
+<a class="externalLink" href="http://jackrabbit.apache.org/api/1.5/org/apache/jackrabbit/core/fs/local/LocalFileSystem.html">LocalFileSystem</a>,
+<a class="externalLink" href="http://jackrabbit.apache.org/api/1.5/org/apache/jackrabbit/core/fs/db/DatabaseFileSystem.html">DatabaseFileSystem</a> (including subclasses),
+and <a class="externalLink" href="http://jackrabbit.apache.org/api/1.5/org/apache/jackrabbit/core/fs/mem/MemoryFileSystem.html">MemoryFileSystem</a>
+for the available options. The recommended alternative is to use the
+<code>LocalFileSystem</code> implementation that simply maps abstract file system
+accesses to the specified directory within the native file system.</p></section><section>
+<h2><a name="Cluster_configuration"></a><a name="cluster-configuration"></a>
+Cluster configuration</h2>
<p>See the <a class="externalLink" href="http://jackrabbit.apache.org/archive/wiki/JCR/Clustering_115513377.html">Clustering</a> page on the Jackrabbit wiki.</p></section><section>
-<h2><a name="Data_store_configuration"></a><a name="datastore-configuration"></a> Data store configuration</h2>
+<h2><a name="Data_store_configuration"></a><a name="datastore-configuration"></a>
+Data store configuration</h2>
<p>See the <a class="externalLink" href="http://jackrabbit.apache.org/archive/wiki/JCR/DataStore_115513387.html">DataStore</a> page on the Jackrabbit wiki.</p></section><section>
-<h2><a name="Item_state_locking_configuration"></a><a name="itemstatelocking-configuration"></a> Item state locking configuration</h2>
+<h2><a name="Item_state_locking_configuration"></a><a name="itemstatelocking-configuration"></a>
+Item state locking configuration</h2>
<p>TODO</p></section><section>
<h2><a name="Passwords_in_configuration_.28as_of_Jackrabbit_2.3.29"></a>Passwords in configuration (as of Jackrabbit 2.3)</h2>
-<p>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 <code>{base64}</code>. Jackrabbit will automatically decode such a password before passing it to the underlying database.</p>
-<p>As an example, the following two password configuration parameters are equivalent (“dGVzdA==” is the base64 encoding of “test”):</p>
+<p>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 <code>{base64}</code>. Jackrabbit will automatically decode such a password
+before passing it to the underlying database.</p>
+<p>As an example, the following two password configuration parameters are
+equivalent (“dGVzdA==” is the base64 encoding of “test”):</p>
-<div class="source">
-<div class="source"><pre class="prettyprint linenums"><param name="password" value="test"/>
+<div class="source"><pre class="prettyprint linenums"><code><param name="password" value="test"/>
<param name="password" value="{base64}dGVzdA=="/>
-</pre></div></div></section>
+</code></pre></div></section>
</main>
</div>
</div>
@@ -386,10 +512,12 @@ By default Jackrabbit only releases reso
<a href="https://www.apache.org/">The Apache Software Foundation</a> | <a href="https://privacy.apache.org/policies/privacy-policy-public.html">Privacy Policy</a>
</p>
</div>
- <div id="ohloh" class="pull-right">
- <script src="https://www.ohloh.net/p/jackrabbit/widgets/project_users_logo.js"></script>
- </div>
- </div>
+ </div>
</footer>
+<script>
+ if(anchors) {
+ anchors.add();
+ }
+</script>
</body>
</html>
\ No newline at end of file