Author: buildbot Date: Fri Oct 16 14:17:59 2015 New Revision: 969174 Log: Staging update by buildbot for sling
Modified: websites/staging/sling/trunk/content/ (props changed) websites/staging/sling/trunk/content/documentation/the-sling-engine/the-sling-launchpad.html Propchange: websites/staging/sling/trunk/content/ ------------------------------------------------------------------------------ --- cms:source-revision (original) +++ cms:source-revision Fri Oct 16 14:17:59 2015 @@ -1 +1 @@ -1709005 +1709009 Modified: websites/staging/sling/trunk/content/documentation/the-sling-engine/the-sling-launchpad.html ============================================================================== --- websites/staging/sling/trunk/content/documentation/the-sling-engine/the-sling-launchpad.html (original) +++ websites/staging/sling/trunk/content/documentation/the-sling-engine/the-sling-launchpad.html Fri Oct 16 14:17:59 2015 @@ -126,7 +126,6 @@ h2:hover > .headerlink, h3:hover > .head <li><a href="#slingproperties">sling.properties</a></li> <li><a href="#components">Components</a><ul> <li><a href="#launchpad-base">Launchpad Base</a></li> -<li><a href="#launchpad-bundles">Launchpad Bundles</a></li> <li><a href="#launchpad-app-and-launchpad-webapp">Launchpad App and Launchpad WebApp</a></li> </ul> </li> @@ -331,62 +330,22 @@ handed to the <code>Main</code> construc </li> </ul> <p>To build a very basic Sling launcher, the <em>Launchpad Base</em> is actually all you need. But to really glue this together and get a usable system, some more work is required. Lets see how the additionaly projects <em>Launchpad Bundles</em>, <em>Launchpad App</em>, and <em>Launchpad WebApp</em> get to that.</p> -<h3 id="launchpad-bundles">Launchpad Bundles<a class="headerlink" href="#launchpad-bundles" title="Permanent link">¶</a></h3> -<p>The second project we want to look at is the <em>Launchpad Bundles</em> project. This is a very simple project in that it only collects together a number of OSGi bundles, which will make up the final application. The bundles are stored in a (big) Java Archive in folders whose path is formed with <code>resources/9</code> where <code>9</code> is a start level which is assigned to the bundles as they are installed. The special start level <code>0</code> instructs the installer to not actually assign a specific start level to the bundles contained in that folder.</p> -<p>Currently the following start level assignement is used by the <em>Launchpad Bundles</em> project:</p> -<table class="table"> -<thead> -<tr> -<th>Start Level</th> -<th>Bundle Group</th> -<th>Bundle(s)</th> -</tr> -</thead> -<tbody> -<tr> -<td>1</td> -<td>Basic bundles required for the correct operation of Sling</td> -<td>org.apache.sling.commons.log</td> -</tr> -<tr> -<td>5</td> -<td>Apache Felix Web Console</td> -<td>org.apache.felix.bundlerepository, org.apache.felix.webconsole, org.apache.sling.extensions.threaddump</td> -</tr> -<tr> -<td>10</td> -<td>OSGi Compendium Service Implementations</td> -<td>org.apache.felix.configadmin, org.apache.felix.eventadmin, org.apache.felix.metatype, org.apache.felix.scr</td> -</tr> -<tr> -<td>15</td> -<td>JCR Repository (Jackrabbit)</td> -<td>commons-collections, commons-io-1.4.jar, commons-lang, jackrabbit-api, jackrabbit-jcr-commons, org.apache.sling.commons.mime, org.apache.sling.commons.osgi, org.apache.sling.jcr.api, org.apache.sling.jcr.base, org.apache.sling.jcr.jackrabbit.server, org.apache.sling.jcr.webdav</td> -</tr> -<tr> -<td>0</td> -<td>Actual Sling Application bundles</td> -<td>org.apache.sling.adapter, org.apache.sling.api, org.apache.sling.bundleresource.impl, org.apache.sling.commons.json, org.apache.sling.engine, org.apache.sling.extensions.apt.parser, org.apache.sling.extensions.apt.servlet, org.apache.sling.httpauth, org.apache.sling.jcr.classloader, org.apache.sling.jcr.contentloader, org.apache.sling.jcr.ocm, org.apache.sling.jcr.resource, org.apache.sling.launchpad.content, org.apache.sling.samples.path-based.rtp, org.apache.sling.scripting.api, org.apache.sling.scripting.core, org.apache.sling.scripting.javascript, org.apache.sling.scripting.jsp, org.apache.sling.scripting.jsp.taglib, org.apache.sling.servlets.get, org.apache.sling.servlets.post, org.apache.sling.servlets.resolver</td> -</tr> -</tbody> -</table> <h3 id="launchpad-app-and-launchpad-webapp">Launchpad App and Launchpad WebApp<a class="headerlink" href="#launchpad-app-and-launchpad-webapp" title="Permanent link">¶</a></h3> <p>The <em>Launchpad App</em> and <em>Launchpad WebApp</em> bundles are actually projects which just glue together artifacts from the Launchpad projects. There is nothing special about them. Here's what is done:</p> <ul> <li>Take the appropriate secondary artifact from the <em>Launchpad Base</em> project: <em>app</em> for the Standalone Java Application or <em>webapp</em> for the Web Application and unpack</li> <li>Take the <em>Launchpad Base</em> primary artifact and place it under the name <code>org.apache.sling.launchpad.base.jar</code> into the <code>resources</code> folder</li> -<li>Take the <em>Launchpad Bundles</em> artifact and unpack it</li> +<li>Copies the list of artifacts defined in the <a href="/documentation/development/slingstart.html">Provisioning model</a> </li> <li>Finally pack all together into a single big JAR or WAR file</li> </ul> -<p>The artifacts can be configured to use different JCR repository implementations, based on the value of the <code>-Dsling.run.modes</code> property. The following run modes are available for the 8-SNAPSHOT version of the Sling Launchpad:</p> +<p>The artifacts can be configured to use different JCR repository implementations, based on the value of the <code>-Dsling.run.modes</code> property. The following run modes are available for the 8 version of the Sling Launchpad:</p> <ul> -<li><code>jackrabbit</code> ( default ): configures and starts up an Apache Jackrabbit 2.x JCR repository implementation</li> <li><code>oak</code>: configures and starts up an Apache Jackrabbit Oak repository implementation with a SegmentNodeStore ( TarMK ) implementation</li> <li><code>oak,oak_mongo</code>: configures and starts up an Apache Jackrabbit Oak repository implementation with a DocumentNodeStore implementation connected to a MongoDB database. The default configuration points to a MongoDB instance at mongodb://localhost:27017 and a database named sling.</li> </ul> -<p>That's it. The resulting artifact may be directly used to launch the Standalone Java Application or may directly be deployed into any Servlet API 2.4 (or later) compliant servlet container.</p> +<p>That's it. The resulting artifact may be directly used to launch the Standalone Java Application or may directly be deployed into any Servlet API 3.0 (or later) compliant servlet container.</p> <div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;"> - Rev. 1707135 by rombert on Tue, 6 Oct 2015 20:27:49 +0000 + Rev. 1709009 by rombert on Fri, 16 Oct 2015 14:17:43 +0000 </div> <div class="trademarkFooter"> Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project