sling-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1615921 - /sling/site/trunk/content/documentation/bundles/osgi-installer.mdtext
Date Tue, 05 Aug 2014 12:57:40 GMT
Author: bdelacretaz
Date: Tue Aug  5 12:57:40 2014
New Revision: 1615921

add installer API info


Modified: sling/site/trunk/content/documentation/bundles/osgi-installer.mdtext
--- sling/site/trunk/content/documentation/bundles/osgi-installer.mdtext (original)
+++ sling/site/trunk/content/documentation/bundles/osgi-installer.mdtext Tue Aug  5 12:57:40
@@ -14,6 +14,13 @@ As the OSGi installer itself is not perf
 It's possible to add own providers, transformers and installer factories to support custom
+## API
+The installer API is defined by the `` package 
+of the [](
module. The main
+interface is the `OsgiInstaller` with which installable resources can be registered.
+The [installer integration tests][1] module can be useful to understand the details of how
the installer works.
 ## Artifact Handling
 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.
@@ -43,3 +50,6 @@ During development, SNAPSHOT versions sh
 ## Configuration Handling
 In general the OSGi installer installs the configuration with the highest priority. For example
in combination with the JCR installer provider, a configuration from */apps* is preferred
over a configuration for the same service from */libs*.
+  [1]:
\ No newline at end of file

View raw message