sling-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r918458 - in /websites/staging/sling/trunk/content: ./ documentation/bundles/osgi-installer.html
Date Tue, 05 Aug 2014 12:57:50 GMT
Author: buildbot
Date: Tue Aug  5 12:57:50 2014
New Revision: 918458

Staging update by buildbot for sling

    websites/staging/sling/trunk/content/   (props changed)

Propchange: websites/staging/sling/trunk/content/
--- cms:source-revision (original)
+++ cms:source-revision Tue Aug  5 12:57:50 2014
@@ -1 +1 @@

Modified: websites/staging/sling/trunk/content/documentation/bundles/osgi-installer.html
--- websites/staging/sling/trunk/content/documentation/bundles/osgi-installer.html (original)
+++ websites/staging/sling/trunk/content/documentation/bundles/osgi-installer.html Tue Aug
 5 12:57:50 2014
@@ -96,6 +96,11 @@
 <p>A provider is just scanning for artifacts and their removal. It informs the OSGi
installer about new artifacts and removed artifacts. The provider itself has usually no knowledge
about the contents of an artifact. It does not know about bundles, configurations etc.</p>
 <p>As the OSGi installer itself is not performing the actual install, update or removal
of an artifact, its possible to install transformers and installer factories. A transformer
inspects the artifacts and tries to detect its type. By default, detecting of bundles and
configurations is supported. The final service is an installer factory creating the actual
task, like install this bundle, update that bundle etc.</p>
 <p>It's possible to add own providers, transformers and installer factories to support
custom scenarios.</p>
+<h2 id="api">API</h2>
+<p>The installer API is defined by the <code></code>
+of the <a href=""></a>
module. The main
+interface is the <code>OsgiInstaller</code> with which installable resources
can be registered.</p>
+<p>The <a href="">installer
integration tests</a> module can be useful to understand the details of how the installer
 <h2 id="artifact-handling">Artifact Handling</h2>
 <p>Once an artifact is detected by a transformer, it gets a unique id. By default a
bundle gets the symbolic name as the unique identifier and a configuration the PID.
 In addition to this id, an artifact gets a priority information from the provider. The priority
is used if an artifact with the same id is provided several times from different locations.
For example if a file system provider is scanning two directories and an artifact with the
same id (like a configuration) is added to both directories, one should have precedence over
the other. This is handled by the priority.</p>
@@ -115,7 +120,7 @@ If an installed bundle is managed via an
 <h2 id="configuration-handling">Configuration Handling</h2>
 <p>In general the OSGi installer installs the configuration with the highest priority.
For example in combination with the JCR installer provider, a configuration from <em>/apps</em>
is preferred over a configuration for the same service from <em>/libs</em>.</p>
       <div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
-        Rev. 1599909 by dklco on Wed, 4 Jun 2014 05:31:41 +0000
+        Rev. 1615921 by bdelacretaz on Tue, 5 Aug 2014 12:57:40 +0000
       <div class="trademarkFooter"> 
         Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project

View raw message