Author: buildbot
Date: Fri Oct 7 08:03:29 2016
New Revision: 998994
Log:
Staging update by buildbot for sling
Modified:
websites/staging/sling/trunk/content/ (props changed)
websites/staging/sling/trunk/content/documentation/bundles/jcr-installer-provider.html
Propchange: websites/staging/sling/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Oct 7 08:03:29 2016
@@ -1 +1 @@
-1763312
+1763692
Modified:
websites/staging/sling/trunk/content/documentation/bundles/jcr-installer-provider.html
==============================================================================
---
websites/staging/sling/trunk/content/documentation/bundles/jcr-installer-provider.html
(original)
+++
websites/staging/sling/trunk/content/documentation/bundles/jcr-installer-provider.html
Fri Oct 7 08:03:29 2016
@@ -117,7 +117,8 @@ h2:hover > .headerlink, h3:hover > .head
<p>The JCR installer provider scans the JCR repository for artifacts and
provides them to the <a href="/documentation/bundles/osgi-installer.html">OSGI
installer</a>.</p>
<h2 id="configuration-and-scanning">Configuration and Scanning<a
class="headerlink" href="#configuration-and-scanning" title="Permanent
link">¶</a></h2>
<p>The JCR installer provider can be configured with weighted paths which are
scanned. By default, the installer scans in <em>/apps</em> and <em>/libs</em>
where artifacts found in <em>/apps</em> get a higher priority. The installer
does a deep scan and uses a regular expression to detect folders containing
artifacts to be installed. By default, artifacts from within a folder named
<em>install</em> are provided to the OSGi installer.</p>
-<p>If such an install folder contains a binary artifact (e.g. a bundle) this
is provided to the OSGi installer. In addition a node of type
<em>sling:OsgiConfig</em> is provided as a configuration to the installer.</p>
+<p>If such an install folder contains a binary artifact (e.g. a bundle or a
config file as described in <a
href="/documentation/bundles/configuration-installer-factory.html">Configuration
Installer Factory</a> this is provided to the OSGi installer. </p>
+<p>In addition every node of type <em>sling:OsgiConfig</em> is provided as a
configuration to the installer. This has the advantage of leveraging the JCR
structure better than binary files, but has the known limitations outlined in
<a href="https://issues.apache.org/jira/browse/SLING-4183";>SLING-4183</a> and
<a href="https://issues.apache.org/jira/browse/SLING-2477";>SLING-2477</a>,
therefore it is recommended to stick to one of the binary formats described in
<a
href="/documentation/bundles/configuration-installer-factory.html">Configuration
Installer Factory</a>.</p>
<p>The JCR installer provider does not check or scan the artifacts itself, the
detection and installation is deferred to the OSGi installer.</p>
<h3 id="runmode-support">Runmode Support<a class="headerlink"
href="#runmode-support" title="Permanent link">¶</a></h3>
<p>The JCR installer supports run modes for installing artifacts. By default
folders named <em>install</em> are checked for artifacts. If Apache Sling is
started with one (or more run modes), all folders named
<em>install.[RUNMODE]</em> are scanned as well. To be precise, the folder name
can be followed by any number of run modes separated by comma. For example, if
started with run modes <em>dev</em>, <em>a1</em>, and <em>public</em>, folders
like <em>install.dev</em>, <em>install.a1</em>, <em>install.public</em> are
searched as well as <em>install.dev.a1</em>, or <em>install.a1.dev</em>.</p>
@@ -125,7 +126,7 @@ h2:hover > .headerlink, h3:hover > .head
<h2 id="write-back-support">Write Back Support<a class="headerlink"
href="#write-back-support" title="Permanent link">¶</a></h2>
<p>The JCR installer supports writing back of configurations which are changed
by some other ways, e.g by using the Apache Felix web console. If this is a new
configuration which was not originally stored in the repository, a new
configuration is stored under <em>/apps/sling/install</em>. The highest search
path is used together with a configurable folder (<em>sling/install</em> in
this case).
If a configuration is changed which already exists in the repository, then it
depends where the original configuration is stored. If its under <em>/libs</em>
a new configuration at the same path under <em>/apps</em> is created. Otherwise
the configuration is directly modified.
-As JCR properties do not support all Java primitive types like Integer, the
write back does not generate a node in the repository but a properties file.</p>
+As JCR properties do not support all Java primitive types like Integer, the
write back does not generate a node of type <em>sling:OsgiConfig</em> in the
repository but a properties file as described in <a
href="/documentation/bundles/configuration-installer-factory.html">Configuration
Installer Factory</a>.</p>
<p>Write back can be turned off by configuration.</p>
<h3 id="start-level-support">Start Level Support<a class="headerlink"
href="#start-level-support" title="Permanent link">¶</a></h3>
<p>If the parent folder of a bundle has a name which is a number, this is used
as the start level (when installing the bundle for the first time, compare with
<a href="https://issues.apache.org/jira/browse/SLING-2011";>SLING-2011</a>). So
e.g. a bundle in the path <code>/libs/sling/install/15/somebundle.jar</code> is
having the start level <strong>15</strong>. </p>
@@ -232,7 +233,7 @@ As JCR properties do not support all Jav
<li>JCR installer provider (<a
href="http://svn.apache.org/repos/asf/sling/trunk/installer/providers/jcr";>org.apache.sling.installer.provider.jcr</a>)</li>
</ul>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1705981 by cziegeler on Wed, 30 Sep 2015 08:33:31 +0000
+ Rev. 1763692 by kwin on Fri, 7 Oct 2016 08:03:12 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache
Sling project
