felix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r971304 [5/10] - in /websites/staging/felix/trunk/content: ./ apidocs/ documentation/ documentation/community/ documentation/development/ documentation/faqs/ documentation/subprojects/ documentation/subprojects/apache-felix-commons/ documen...
Date Wed, 04 Nov 2015 07:43:19 GMT
Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-osgi-r4-2-ct-results.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-osgi-r4-2-ct-results.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-osgi-r4-2-ct-results.html Wed Nov  4 07:43:11 2015
@@ -50,17 +50,17 @@
   visibility: hidden;
 }
 h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
-<p><a href="/news.html">news</a>  <br />
-<a href="/license.html">license</a>  <br />
-<a href="/downloads.cgi">downloads</a>  <br />
-<a href="/documentation.html">documentation</a>  <br />
-<a href="/mailinglists.html">mailing lists</a>  <br />
-<a href="/documentation/community/contributing.html">contributing</a>  <br />
-<a href="/sitemap.html">site map</a>  <br />
-<a href="http://www.apache.org/">asf</a>  <br />
-<a href="http://www.apache.org/security/">security</a>  <br />
-<a href="http://www.apache.org/foundation/sponsorship.html">sponsorship</a>  <br />
-<a href="http://www.apache.org/foundation/thanks.html">sponsors</a>    </p>
+<p><a href="/news.html">News</a>  <br />
+<a href="/license.html">License</a>  <br />
+<a href="/downloads.cgi">Downloads</a>  <br />
+<a href="/documentation.html">Documentation</a>  <br />
+<a href="/mailinglists.html">Mailing Lists</a>  <br />
+<a href="/documentation/community/contributing.html">Contributing</a>  <br />
+<a href="/sitemap.html">Site Map</a>  <br />
+<a href="http://www.apache.org/">ASF</a>  <br />
+<a href="http://www.apache.org/security/">Security</a>  <br />
+<a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a>  <br />
+<a href="http://www.apache.org/foundation/thanks.html">Sponsors</a>    </p>
 <iframe
     src="http://www.apache.org/ads/button.html"
     style="border-width:0; float: left"

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-osgi-r4-3-ct-results.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-osgi-r4-3-ct-results.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-osgi-r4-3-ct-results.html Wed Nov  4 07:43:11 2015
@@ -50,17 +50,17 @@
   visibility: hidden;
 }
 h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
-<p><a href="/news.html">news</a>  <br />
-<a href="/license.html">license</a>  <br />
-<a href="/downloads.cgi">downloads</a>  <br />
-<a href="/documentation.html">documentation</a>  <br />
-<a href="/mailinglists.html">mailing lists</a>  <br />
-<a href="/documentation/community/contributing.html">contributing</a>  <br />
-<a href="/sitemap.html">site map</a>  <br />
-<a href="http://www.apache.org/">asf</a>  <br />
-<a href="http://www.apache.org/security/">security</a>  <br />
-<a href="http://www.apache.org/foundation/sponsorship.html">sponsorship</a>  <br />
-<a href="http://www.apache.org/foundation/thanks.html">sponsors</a>    </p>
+<p><a href="/news.html">News</a>  <br />
+<a href="/license.html">License</a>  <br />
+<a href="/downloads.cgi">Downloads</a>  <br />
+<a href="/documentation.html">Documentation</a>  <br />
+<a href="/mailinglists.html">Mailing Lists</a>  <br />
+<a href="/documentation/community/contributing.html">Contributing</a>  <br />
+<a href="/sitemap.html">Site Map</a>  <br />
+<a href="http://www.apache.org/">ASF</a>  <br />
+<a href="http://www.apache.org/security/">Security</a>  <br />
+<a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a>  <br />
+<a href="http://www.apache.org/foundation/thanks.html">Sponsors</a>    </p>
 <iframe
     src="http://www.apache.org/ads/button.html"
     style="border-width:0; float: left"

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-usage-documentation.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-usage-documentation.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-usage-documentation.html Wed Nov  4 07:43:11 2015
@@ -39,17 +39,28 @@
     </div>
     
     <div class="menu"> 
-      <p><a href="/news.html">news</a>  <br />
-<a href="/license.html">license</a>  <br />
-<a href="/downloads.cgi">downloads</a>  <br />
-<a href="/documentation.html">documentation</a>  <br />
-<a href="/mailinglists.html">mailing lists</a>  <br />
-<a href="/documentation/community/contributing.html">contributing</a>  <br />
-<a href="/sitemap.html">site map</a>  <br />
-<a href="http://www.apache.org/">asf</a>  <br />
-<a href="http://www.apache.org/security/">security</a>  <br />
-<a href="http://www.apache.org/foundation/sponsorship.html">sponsorship</a>  <br />
-<a href="http://www.apache.org/foundation/thanks.html">sponsors</a>    </p>
+      <style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p><a href="/news.html">News</a>  <br />
+<a href="/license.html">License</a>  <br />
+<a href="/downloads.cgi">Downloads</a>  <br />
+<a href="/documentation.html">Documentation</a>  <br />
+<a href="/mailinglists.html">Mailing Lists</a>  <br />
+<a href="/documentation/community/contributing.html">Contributing</a>  <br />
+<a href="/sitemap.html">Site Map</a>  <br />
+<a href="http://www.apache.org/">ASF</a>  <br />
+<a href="http://www.apache.org/security/">Security</a>  <br />
+<a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a>  <br />
+<a href="http://www.apache.org/foundation/thanks.html">Sponsors</a>    </p>
 <iframe
     src="http://www.apache.org/ads/button.html"
     style="border-width:0; float: left"
@@ -66,7 +77,18 @@
       </div>
 
       <h1>Apache Felix Framework Usage Documentation</h1>
-      <ul>
+      <style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<ul>
 <li><a href="#downloading-the-framework">Downloading the Framework</a></li>
 <li><a href="#starting-the-framework">Starting the Framework</a></li>
 <li><a href="#framework-shell">Framework Shell</a><ul>
@@ -82,9 +104,9 @@
 <li><a href="#configuring-bundles">Configuring Bundles</a></li>
 <li><a href="#feedback">Feedback</a></li>
 </ul>
-<h2 id="downloading-the-framework">Downloading the Framework</h2>
+<h2 id="downloading-the-framework">Downloading the Framework<a class="headerlink" href="#downloading-the-framework" title="Permanent link">&para;</a></h2>
 <p>Go to the <a href="">downloads</a> page and download the latest Felix framework distribution.</p>
-<h2 id="starting-the-framework">Starting the Framework</h2>
+<h2 id="starting-the-framework">Starting the Framework<a class="headerlink" href="#starting-the-framework" title="Permanent link">&para;</a></h2>
 <p>Start the framework from the installation directory by typing:</p>
 <div class="codehilite"><pre><span class="n">java</span> <span class="o">-</span><span class="n">jar</span> <span class="n">bin</span><span class="o">/</span><span class="n">felix</span><span class="p">.</span><span class="n">jar</span>
 </pre></div>
@@ -109,7 +131,7 @@ Now, if you start Felix with something l
 the launcher.
 </div>
 
-<h2 id="framework-shell">Framework Shell</h2>
+<h2 id="framework-shell">Framework Shell<a class="headerlink" href="#framework-shell" title="Permanent link">&para;</a></h2>
 <p>The main way to interact with the framework is via the supplied Apache Felix Gogo shell. After starting the framework, type <code>help</code> into the shell to see the list of the available commands and <code>help &lt;command-name&gt;</code> to get help for a specific command.</p>
 <div class="info" markdown="1">
 <b>Useful Information</b><br/>
@@ -120,7 +142,7 @@ then you must either type the full <code
 </div>
 
 <p>To install bundles, use the <code>felix:install</code> command, which is described in more detail in the next <a href="">sub-section</a>. To list installed bundles, use the <code>felix:lb</code> command. To stop the framework type <code>stop 0</code> to stop the System Bundle; any installed bundles will automatically be reloaded (and potentially restarted) the next time you launch with the associated cache.</p>
-<h3 id="installing-bundles">Installing Bundles</h3>
+<h3 id="installing-bundles">Installing Bundles<a class="headerlink" href="#installing-bundles" title="Permanent link">&para;</a></h3>
 <p>A bundle is the OSGi term for a component for the OSGi framework. A bundle is simply a JAR file containing a manifest and some combination of Java classes, embedded JAR files, native code, and resources. A bundle may provide some specific functionality for the user or it may implement a service that other bundles can use; bundles can only use functionality from other bundles through shared services and packages.</p>
 <p>The Felix framework distribution comes with three bundles, which are located in the <code>bundle/</code> directory of the framework distribution installation directory. These bundles include the Gogo Runtime (core command processing functionality), Gogo Shell (text-based shell user interface), Gogo Command (basic set of commands), and Bundle Repository (a bundle repository service). In addition to these bundles, the bundle repository provides access to other bundles for easy installation. The bundle repository service provides a set of shell commands in the <code>obr:*</code> scope; refer to the <a href="/documentation/subprojects/apache-felix-osgi-bundle-repository.html">Apache Felix OSGi Bundle Repository</a> for more information.</p>
 <p>Before installing any bundles, it is important to understand how bundles are manually deployed into the framework. Bundles are deployed in two stages; first they are installed, then they are started. To install a bundle use the <code>felix:install</code> shell command followed by a bundle URL. For example, to install a <code>bundle.jar</code> bundle you type:</p>
@@ -158,7 +180,7 @@ specification.
 </div>
 
 <p>For an introduction to writing bundles and services, refer to the Felix bundle tutorial.</p>
-<h3 id="web-proxy-issues-when-installing-bundles">Web Proxy Issues when Installing Bundles</h3>
+<h3 id="web-proxy-issues-when-installing-bundles">Web Proxy Issues when Installing Bundles<a class="headerlink" href="#web-proxy-issues-when-installing-bundles" title="Permanent link">&para;</a></h3>
 <p>If you use a proxy for Web access, then you may run into difficulty using the Gogo shell to install bundles from remote URLs. To remedy this situation, certain system properties must be set to make the framework work with your proxy. These properties are:</p>
 <ul>
 <li><code>http.proxyHost</code> - the name of the proxy host.</li>
@@ -168,7 +190,7 @@ specification.
 <p>These system properties can be set directly on the command line when starting the JVM using the standard "<code>\-D&lt;prop&gt;=&lt;value&gt;</code>" syntax
 or you can put them in the <code>lib/system.properties</code> file of your Felix installation; see the next section on <a href="#configuring-the-framework">configuring Felix</a>
 for more information.</p>
-<h2 id="bundle-auto-deploy">Bundle Auto-Deploy</h2>
+<h2 id="bundle-auto-deploy">Bundle Auto-Deploy<a class="headerlink" href="#bundle-auto-deploy" title="Permanent link">&para;</a></h2>
 <p>To minimize the amount of configuration necessary to install bundles when you launch the framework, the Felix launcher uses the concept of an "auto-deploy" directory. The Felix launcher deploys all bundles in the auto-deploy directory into the framework instance during startup. By default, the auto-deploy directory is "<code>bundle</code>" in the current directory, but it can be specified on the command line like this:</p>
 <div class="codehilite"><pre><span class="n">java</span> <span class="o">-</span><span class="n">jar</span> <span class="n">bin</span><span class="o">/</span><span class="n">felix</span><span class="p">.</span><span class="n">jar</span> <span class="o">-</span><span class="n">b</span> <span class="o">/</span><span class="n">path</span><span class="o">/</span><span class="n">to</span><span class="o">/</span><span class="n">dir</span>
 </pre></div>
@@ -180,7 +202,7 @@ for more information.</p>
 <li><code>felix.auto.deploy.action</code> - Specifies the auto-deploy actions to be performed on the bundle JAR files found in the auto-deploy directory. The possible actions are <code>install</code>, <code>update</code>, <code>start</code>, and <code>uninstall</code>. If no actions are specified, then the auto-deploy directory is not processed (i.e., it is disabled). There is no default value for this property, but the default <code>config.properties</code> file installed with the Felix framework distribution sets the value to: <code>install, start</code></li>
 </ul>
 <p>The next section describes how to set and use configuration properties.</p>
-<h2 id="configuring-the-framework">Configuring the Framework</h2>
+<h2 id="configuring-the-framework">Configuring the Framework<a class="headerlink" href="#configuring-the-framework" title="Permanent link">&para;</a></h2>
 <p>Both the Felix framework and the launcher use configuration properties to alter their default behavior. The framework can only be configured by passing properties into its constructor, but the launcher provides a mechanism to configure the framework via a property file. The framework launcher reads configuration properties from <code>conf/config.properties</code>. This file uses standard Java property file syntax.</p>
 <p>The launcher also supports setting system properties via the <code>conf/system.properties</code> file. This file is purely for convenience when you need to repeatedly set system properties when running the framework. While the framework itself does not look at system properties, the launcher does copy any framework configuration properties found in the system properties into the framework configuration map, also for your convenience.</p>
 <p>It is possible to specify different locations for these property files using the <code>felix.config.properties</code> and <code>felix.system.properties</code> system properties when executing the framework. For example:</p>
@@ -189,12 +211,12 @@ for more information.</p>
 
 
 <p>Configuration and system properties are accessible at run time via <code>BundleContext.getProperty()</code>, but configuration properties override system properties. For more information about available configuration properties, refer to the <a href="/documentation/subprojects/apache-felix-framework/apache-felix-framework-configuration-properties.html">Apache Felix Framework Configuration Properties</a> document. The Felix framework distribution contains a default <code>conf/config.properties</code>.</p>
-<h3 id="system-property-substitution">System Property Substitution</h3>
+<h3 id="system-property-substitution">System Property Substitution<a class="headerlink" href="#system-property-substitution" title="Permanent link">&para;</a></h3>
 <p>It is possible to use system properties to specify the values of properties in the <code>conf/config.properties</code> file. This is achieved through system property substitution, which is instigated by using <code>$\{&lt;property&gt;\</code>} syntax, where <code>&lt;property&gt;</code> is the name of a system property to substitute. When the properties file is read, any such property values are substituted as appropriate. It is possible to have nested system property substitution, in which case the inner-most property is substituted first, then the next inner most, until reaching the outer most.</p>
-<h2 id="configuring-bundles">Configuring Bundles</h2>
+<h2 id="configuring-bundles">Configuring Bundles<a class="headerlink" href="#configuring-bundles" title="Permanent link">&para;</a></h2>
 <p>Some bundles use properties to configure certain aspects of their behavior. It is a good idea, when implementing bundles, to parameterize them with properties where appropriate. To learn about the configuration options for specific bundles, refer to the documentation that accompanies them.</p>
 <p>Bundle properties may also be defined in the <code>conf/config.properties</code> property file. Any property placed in this file will be accessible via <code>BundleContext.getProperty()</code> at run time. The property file uses the standard Java property file syntax (i.e., attribute-value pairs). For information on changing the default location of this file, refer to the section on <a href="#configuring-the-framework">configuring Felix</a>.</p>
-<h2 id="feedback">Feedback</h2>
+<h2 id="feedback">Feedback<a class="headerlink" href="#feedback" title="Permanent link">&para;</a></h2>
 <p>Subscribe to the Felix users mailing list by sending a message to <a href="mailto:users-subscribe@felix.apache.org">users-subscribe@felix.apache.org</a>;
 after subscribing, email questions or feedback to <a href="mailto:users@felix.apache.org">users@felix.apache.org</a>.</p>
       <div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-gogo.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-gogo.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-gogo.html Wed Nov  4 07:43:11 2015
@@ -50,17 +50,17 @@
   visibility: hidden;
 }
 h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
-<p><a href="/news.html">news</a>  <br />
-<a href="/license.html">license</a>  <br />
-<a href="/downloads.cgi">downloads</a>  <br />
-<a href="/documentation.html">documentation</a>  <br />
-<a href="/mailinglists.html">mailing lists</a>  <br />
-<a href="/documentation/community/contributing.html">contributing</a>  <br />
-<a href="/sitemap.html">site map</a>  <br />
-<a href="http://www.apache.org/">asf</a>  <br />
-<a href="http://www.apache.org/security/">security</a>  <br />
-<a href="http://www.apache.org/foundation/sponsorship.html">sponsorship</a>  <br />
-<a href="http://www.apache.org/foundation/thanks.html">sponsors</a>    </p>
+<p><a href="/news.html">News</a>  <br />
+<a href="/license.html">License</a>  <br />
+<a href="/downloads.cgi">Downloads</a>  <br />
+<a href="/documentation.html">Documentation</a>  <br />
+<a href="/mailinglists.html">Mailing Lists</a>  <br />
+<a href="/documentation/community/contributing.html">Contributing</a>  <br />
+<a href="/sitemap.html">Site Map</a>  <br />
+<a href="http://www.apache.org/">ASF</a>  <br />
+<a href="http://www.apache.org/security/">Security</a>  <br />
+<a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a>  <br />
+<a href="http://www.apache.org/foundation/thanks.html">Sponsors</a>    </p>
 <iframe
     src="http://www.apache.org/ads/button.html"
     style="border-width:0; float: left"

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-gogo/rfc-147-overview.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-gogo/rfc-147-overview.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-gogo/rfc-147-overview.html Wed Nov  4 07:43:11 2015
@@ -50,17 +50,17 @@
   visibility: hidden;
 }
 h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
-<p><a href="/news.html">news</a>  <br />
-<a href="/license.html">license</a>  <br />
-<a href="/downloads.cgi">downloads</a>  <br />
-<a href="/documentation.html">documentation</a>  <br />
-<a href="/mailinglists.html">mailing lists</a>  <br />
-<a href="/documentation/community/contributing.html">contributing</a>  <br />
-<a href="/sitemap.html">site map</a>  <br />
-<a href="http://www.apache.org/">asf</a>  <br />
-<a href="http://www.apache.org/security/">security</a>  <br />
-<a href="http://www.apache.org/foundation/sponsorship.html">sponsorship</a>  <br />
-<a href="http://www.apache.org/foundation/thanks.html">sponsors</a>    </p>
+<p><a href="/news.html">News</a>  <br />
+<a href="/license.html">License</a>  <br />
+<a href="/downloads.cgi">Downloads</a>  <br />
+<a href="/documentation.html">Documentation</a>  <br />
+<a href="/mailinglists.html">Mailing Lists</a>  <br />
+<a href="/documentation/community/contributing.html">Contributing</a>  <br />
+<a href="/sitemap.html">Site Map</a>  <br />
+<a href="http://www.apache.org/">ASF</a>  <br />
+<a href="http://www.apache.org/security/">Security</a>  <br />
+<a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a>  <br />
+<a href="http://www.apache.org/foundation/thanks.html">Sponsors</a>    </p>
 <iframe
     src="http://www.apache.org/ads/button.html"
     style="border-width:0; float: left"

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-http-service.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-http-service.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-http-service.html Wed Nov  4 07:43:11 2015
@@ -50,17 +50,17 @@
   visibility: hidden;
 }
 h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
-<p><a href="/news.html">news</a>  <br />
-<a href="/license.html">license</a>  <br />
-<a href="/downloads.cgi">downloads</a>  <br />
-<a href="/documentation.html">documentation</a>  <br />
-<a href="/mailinglists.html">mailing lists</a>  <br />
-<a href="/documentation/community/contributing.html">contributing</a>  <br />
-<a href="/sitemap.html">site map</a>  <br />
-<a href="http://www.apache.org/">asf</a>  <br />
-<a href="http://www.apache.org/security/">security</a>  <br />
-<a href="http://www.apache.org/foundation/sponsorship.html">sponsorship</a>  <br />
-<a href="http://www.apache.org/foundation/thanks.html">sponsors</a>    </p>
+<p><a href="/news.html">News</a>  <br />
+<a href="/license.html">License</a>  <br />
+<a href="/downloads.cgi">Downloads</a>  <br />
+<a href="/documentation.html">Documentation</a>  <br />
+<a href="/mailinglists.html">Mailing Lists</a>  <br />
+<a href="/documentation/community/contributing.html">Contributing</a>  <br />
+<a href="/sitemap.html">Site Map</a>  <br />
+<a href="http://www.apache.org/">ASF</a>  <br />
+<a href="http://www.apache.org/security/">Security</a>  <br />
+<a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a>  <br />
+<a href="http://www.apache.org/foundation/thanks.html">Sponsors</a>    </p>
 <iframe
     src="http://www.apache.org/ads/button.html"
     style="border-width:0; float: left"

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-inventory.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-inventory.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-inventory.html Wed Nov  4 07:43:11 2015
@@ -39,17 +39,28 @@
     </div>
     
     <div class="menu"> 
-      <p><a href="/news.html">news</a>  <br />
-<a href="/license.html">license</a>  <br />
-<a href="/downloads.cgi">downloads</a>  <br />
-<a href="/documentation.html">documentation</a>  <br />
-<a href="/mailinglists.html">mailing lists</a>  <br />
-<a href="/documentation/community/contributing.html">contributing</a>  <br />
-<a href="/sitemap.html">site map</a>  <br />
-<a href="http://www.apache.org/">asf</a>  <br />
-<a href="http://www.apache.org/security/">security</a>  <br />
-<a href="http://www.apache.org/foundation/sponsorship.html">sponsorship</a>  <br />
-<a href="http://www.apache.org/foundation/thanks.html">sponsors</a>    </p>
+      <style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p><a href="/news.html">News</a>  <br />
+<a href="/license.html">License</a>  <br />
+<a href="/downloads.cgi">Downloads</a>  <br />
+<a href="/documentation.html">Documentation</a>  <br />
+<a href="/mailinglists.html">Mailing Lists</a>  <br />
+<a href="/documentation/community/contributing.html">Contributing</a>  <br />
+<a href="/sitemap.html">Site Map</a>  <br />
+<a href="http://www.apache.org/">ASF</a>  <br />
+<a href="http://www.apache.org/security/">Security</a>  <br />
+<a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a>  <br />
+<a href="http://www.apache.org/foundation/thanks.html">Sponsors</a>    </p>
 <iframe
     src="http://www.apache.org/ads/button.html"
     style="border-width:0; float: left"
@@ -66,7 +77,18 @@
       </div>
 
       <h1>Apache Felix Inventory Printer</h1>
-      <p><a id="top"></a></p>
+      <style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p><a id="top"></a></p>
 <div class="toc">
 <ul>
 <li><a href="#introduction">Introduction</a></li>
@@ -86,20 +108,20 @@
 to retrieve inventory information about applications running in an OSGi Framework. Typical information includes currently installed bundles, their state, available configurations, framework properties, log files etc.</p>
 <p>Historically the Inventory Printer evolved from the Web Console Configuration
 Printer framework.</p>
-<h2 id="introduction">Introduction</h2>
+<h2 id="introduction">Introduction<a class="headerlink" href="#introduction" title="Permanent link">&para;</a></h2>
 <p><a href="#top">Top</a></p>
 <p>When trying to find a problem or analyzing the system it would be nice to have a single place to go to and get available information. The Apache Felix inventory bundle tries to exactly fill this gap.</p>
 <p>Originally, the idea started within the Apache Felix WebConsole and it's configuration printers - these pluggable printers allowed to view all available status information in a web browser or download this as zip file. While this already solves most use cases, tying this general functionality to a web console felt wrong, and that's when the inventory module started.</p>
 <p>The current version of the inventory implementation, registers all available InventoryPrinters (see below) as plugins to the web console as this is still the number one use case.</p>
-<h2 id="requirements">Requirements</h2>
+<h2 id="requirements">Requirements<a class="headerlink" href="#requirements" title="Permanent link">&para;</a></h2>
 <p><a href="#top">Top</a></p>
 <p>In and of itself the Apache Felix Inventory Printer module is independent of other modules.</p>
 <p>To actually get access to the output of Inventory Printer services, though, the Apache Felix Web Console must be installed.</p>
 <p>In the future <a href="#gogo-shell">Integration with the Apache Felix Gogo Shell</a> will also be provided in which case the Apache Felix Gogo Shell must be installed.</p>
-<h2 id="inventory-printer-services">Inventory Printer Services</h2>
+<h2 id="inventory-printer-services">Inventory Printer Services<a class="headerlink" href="#inventory-printer-services" title="Permanent link">&para;</a></h2>
 <p><a href="#top">Top</a></p>
 <p>Inventory Printer Services are registered as <code>org.apache.felix.inventory.InventoryPrinter</code> type OSGi services with the following service registration properties:</p>
-<table>
+<table class="table">
 <thead>
 <tr>
 <th>Property</th>
@@ -132,7 +154,7 @@ Printer framework.</p>
 </table>
 <p>The first three properties are required for the Inventory Printer service to be accepted. Otherwise the service is ignored by the framework printing a message to the log.</p>
 <p>To prevent bundle resolution failure if the <code>InventoryPrinter</code> API is not available in the framework it is suggested to register the Inventory Printer services as service factories and dynamically import the API. See the question <a href="#how-to-provide-optional-services"></a> in the Apache Felix OSGi FAQ for more details.</p>
-<h3 id="example-inventory-printer-service">Example Inventory Printer Service</h3>
+<h3 id="example-inventory-printer-service">Example Inventory Printer Service<a class="headerlink" href="#example-inventory-printer-service" title="Permanent link">&para;</a></h3>
 <div class="codehilite"><pre><span class="nd">@Component</span>
 <span class="nd">@Service</span>
 <span class="nd">@Properties</span><span class="o">({</span>
@@ -163,15 +185,15 @@ Printer framework.</p>
 
 
 <p>See also the <a href="/apidocs/inventory/1.0.0/">API JavaDoc</a>.</p>
-<h2 id="zip-attachment-provider">ZIP Attachment Provider</h2>
+<h2 id="zip-attachment-provider">ZIP Attachment Provider<a class="headerlink" href="#zip-attachment-provider" title="Permanent link">&para;</a></h2>
 <p><a href="#top">Top</a></p>
 <p>If an Inventory Printer wants to provide additional contents to an Inventory ZIP File, it can implement the <a href="/apidocs/inventory/1.0.0/org/apache/felix/inventory/ZipAttachmentProvider.html">ZipAttachmentProvider</a> interface and provide additional files when the zip is created.</p>
-<h2 id="configuration-printer-services">Configuration Printer Services</h2>
+<h2 id="configuration-printer-services">Configuration Printer Services<a class="headerlink" href="#configuration-printer-services" title="Permanent link">&para;</a></h2>
 <p><a href="#top">Top</a></p>
 <p>For backwards compatibility the Inventory Printer framework also supports legacy Apache Felix Web Console <code>ConfigurationPrinter</code> services.</p>
 <p>Configuration Printer services are wrapped in an <code>InventoryPrinter</code> adapter and re-registered as Inventory Printer services. Thus they are registered with the Web Console or the Gogo Shell as if the Configuration Printer would be an Inventory Printer.</p>
 <p>Configuration Printer Services are registered as <code>org.apache.felix.webconsole.ConfigurationPrinter</code> type OSGi services with the following service registration properties:</p>
-<table>
+<table class="table">
 <thead>
 <tr>
 <th>Property</th>
@@ -202,16 +224,16 @@ Printer framework.</p>
 </tr>
 </tbody>
 </table>
-<h2 id="integration-with-the-apache-felix-web-console">Integration with the Apache Felix Web Console</h2>
+<h2 id="integration-with-the-apache-felix-web-console">Integration with the Apache Felix Web Console<a class="headerlink" href="#integration-with-the-apache-felix-web-console" title="Permanent link">&para;</a></h2>
 <p><a href="#top">Top</a></p>
 <p>The Inventory Printer framework has first class integration with the Apache Felix Web Console. Each <code>InventoryPrinter</code> service is registered as a plugin in the <code>Inventory</code> category of the Web Console.</p>
 <p>To prevent an Invetory Printer from being registered in the Web Console, the <code>felix.inventory.printer.webconsole</code> service registration property must be set to <code>false</code>.</p>
 <p><a id="gogo-shell"></a></p>
-<h2 id="integration-with-the-apache-felix-gogo-shell">Integration with the Apache Felix Gogo Shell</h2>
+<h2 id="integration-with-the-apache-felix-gogo-shell">Integration with the Apache Felix Gogo Shell<a class="headerlink" href="#integration-with-the-apache-felix-gogo-shell" title="Permanent link">&para;</a></h2>
 <p><a href="#top">Top</a></p>
 <p>Gogo Shell integration is not implemented in the first version of the Apache Felix Inventory Printer module.</p>
 <p>See the issue <a href="https://issues.apache.org/jira/browse/FELIX-4065">FELIX-4065 Provide Gogo Shell integration for InventoryPrinter services</a>.</p>
-<h2 id="issues">Issues</h2>
+<h2 id="issues">Issues<a class="headerlink" href="#issues" title="Permanent link">&para;</a></h2>
 <p><a href="#top">Top</a></p>
 <p>Should you have any questions using the Inventory Printer, please send a
 note to one of our <a href="/mailinglists.html">Mailing Lists</a>.</p>

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/ipojo-advanced-topics/ipojo-extender-configuration.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/ipojo-advanced-topics/ipojo-extender-configuration.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/ipojo-advanced-topics/ipojo-extender-configuration.html Wed Nov  4 07:43:11 2015
@@ -171,7 +171,18 @@
 
     <div class="container">
         <div class="content">
-            <h1 id="configuring-ipojo-extender">Configuring iPOJO Extender</h1>
+            <style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="configuring-ipojo-extender">Configuring iPOJO Extender<a class="headerlink" href="#configuring-ipojo-extender" title="Permanent link">&para;</a></h1>
 <p><em>This page presents how the iPOJO's extender can be configured.</em></p>
 <div class="toc">
 <ul>
@@ -191,9 +202,9 @@
 </li>
 </ul>
 </div>
-<h2 id="extender">Extender</h2>
+<h2 id="extender">Extender<a class="headerlink" href="#extender" title="Permanent link">&para;</a></h2>
 <p>The iPOJO Extender starts with the iPOJO bundle (in fact, it's the iPOJO's <code>BundleActivator</code>). It is basically a <code>BundleTracker</code> that will discover iPOJO's components, instances, etc from the <code>ACTIVE</code> bundles.</p>
-<h3 id="threadpool">ThreadPool</h3>
+<h3 id="threadpool">ThreadPool<a class="headerlink" href="#threadpool" title="Permanent link">&para;</a></h3>
 <p>In Apache Felix iPOJO 1.10, the extender has been refactored to take advantage of multi-threading capabilities of modern machines.
 There is now an <code>ExecutorQueueService</code> service, based on a <code>ThreadPoolExecutor</code> that enable asynchronous (and concurrent) activation of Bundles.
 All activation activities (search for <code>IPOJO-Components</code> and <code>IPOJO-Extensions</code> Manifest headers, creation of factories and instances, binding) are done through job submissions.
@@ -223,13 +234,13 @@ Property names are identical for System
   </tbody>
 </table>
 
-<h3 id="synchronous-asynchronous-processing">Synchronous / Asynchronous processing</h3>
+<h3 id="synchronous-asynchronous-processing">Synchronous / Asynchronous processing<a class="headerlink" href="#synchronous-asynchronous-processing" title="Permanent link">&para;</a></h3>
 <p>By default, Apache Felix iPOJO process the Bundles in an asynchronous way. It's better in term of performances and more aligned with OSGi spec recommendations.
 However, in some situations, like when running in <a href="https://developers.google.com/appengine/">Google App Engine</a> (<em>GAE</em>), the underlying platform imposes limitations.
 For example GAE imposes mono-threading. That means that no asynchronous processing can be done by the application itself.</p>
 <p>In other situations, it can be useful to be sure that components and instances contained in a given Bundle will be synchronously started.</p>
 <p>iPOJO's Extender can be configured to support mono-threaded bundle processing to support such use cases.</p>
-<h4 id="system-wide">System wide</h4>
+<h4 id="system-wide">System wide<a class="headerlink" href="#system-wide" title="Permanent link">&para;</a></h4>
 <p>General synchronous processing can be configured through System properties or iPOJO's own Manifest attributes (requires a dedicated iPOJO bundle build).</p>
 <table class="table table-striped">
   <thead>
@@ -259,7 +270,7 @@ For example GAE imposes mono-threading.
   </tbody>
 </table>
 
-<h4 id="per-bundle">Per-Bundle</h4>
+<h4 id="per-bundle">Per-Bundle<a class="headerlink" href="#per-bundle" title="Permanent link">&para;</a></h4>
 <p>The synchronous behavior can be selected per-bundle (given that it does not conflict with existing system wide configuration).
 Synchronous/Asynchronous behavior can be expressed in the Bundle's Manifest (case is not significant, but an uppercase first letter is recommended):</p>
 <div class="codehilite"><pre><span class="n">IPOJO</span><span class="o">-</span><span class="n">Queue</span><span class="o">-</span><span class="n">Preference</span> <span class="n">SYNC</span>
@@ -273,7 +284,7 @@ Synchronous/Asynchronous behavior can be
 <li><code>DEFAULT</code> using the default behavior</li>
 </ul>
 <p>If no header (or invalid value) is provided, the fallback behavior is <code>DEFAULT</code> (use system wide preference).</p>
-<h3 id="queueservice-insights">QueueService Insights</h3>
+<h3 id="queueservice-insights">QueueService Insights<a class="headerlink" href="#queueservice-insights" title="Permanent link">&para;</a></h3>
 <p>Apache Felix iPOJO provides a mechanism that stores Job events of the QueueService in use (synchronous, multi-threaded, ...) for replay.
 This is very useful to see where time is spent during the bootstrap and take actions accordingly.</p>
 <p>This mechanism is available when the <code>org.apache.felix.ipojo.extender.BootstrapQueueDebug</code> system property is set to <code>true</code>.
@@ -301,7 +312,7 @@ After that, the proxy simply forward the
 </pre></div>
 
 
-<h3 id="event-dispatcher">Event Dispatcher</h3>
+<h3 id="event-dispatcher">Event Dispatcher<a class="headerlink" href="#event-dispatcher" title="Permanent link">&para;</a></h3>
 <p>Apache Felix iPOJO provides a way to circumvent the so-call event storm happening when starting large OSGi applications (chained services apparitions).
 It is a dedicated Event dispatcher that mimics a service registry partition logic based on registered service interfaces (<code>Constants.OBJECTCLASS</code>).
 It is not enabled by default (rely on the framework's own service registry).</p>

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/ipojo-advanced-topics/ipojo-factory-service.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/ipojo-advanced-topics/ipojo-factory-service.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/ipojo-advanced-topics/ipojo-factory-service.html Wed Nov  4 07:43:11 2015
@@ -171,7 +171,18 @@
 
     <div class="container">
         <div class="content">
-            <h1 id="using-the-factory-service-interface">Using the Factory service interface</h1>
+            <style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="using-the-factory-service-interface">Using the Factory service interface<a class="headerlink" href="#using-the-factory-service-interface" title="Permanent link">&para;</a></h1>
 <div class="toc">
 <ul>
 <li><a href="#using-the-factory-service-interface">Using the Factory service interface</a><ul>
@@ -192,17 +203,17 @@
 </div>
 <p>When you declare a component either with <code>@Component</code> or <code>&lt;component&gt;</code>, you are instructing iPOJO to create a <em>factory</em>.</p>
 <p>A factory is an entity managed by iPOJO and responsible for the instance creation and management. Indeed, every time you declare an instance with <code>@Instantiate</code>, <code>&lt;instance&gt;</code> or the configuration admin, you are asking the appropriate factory to create the instance an manage the instance.</p>
-<h2 id="private-vs-public-factories">Private vs. Public factories</h2>
+<h2 id="private-vs-public-factories">Private vs. Public factories<a class="headerlink" href="#private-vs-public-factories" title="Permanent link">&para;</a></h2>
 <p>When you are declaring the component (type), you have the choice between making this factory public or private. Private factories are not accessible, and can only create instances declared from the same bundle. Public factories are accessible from anywhere, and so are able to create instances declared by anyone. They also expose the <code>org.apache.felix.ipojo.Factory</code> service.</p>
 <p>By default, factories are public. However, you can hide them with:</p>
 <div class="codehilite"><pre><span class="nd">@Component</span><span class="o">(</span><span class="n">publicFactory</span><span class="o">=</span><span class="kc">false</span><span class="o">)</span>
 </pre></div>
 
 
-<h2 id="the-factory-service">The Factory service</h2>
+<h2 id="the-factory-service">The Factory service<a class="headerlink" href="#the-factory-service" title="Permanent link">&para;</a></h2>
 <p>Every public factory is exposed as an OSGi service. The
 <a href="http://felix.apache.org/ipojo/api/1.12.1/org/apache/felix/ipojo/Factory.html">org.apache.felix.ipojo.Factory</a> service interface allows you to create and manage instance programmatically.</p>
-<h3 id="finding-and-using-a-factory-service">Finding and using a Factory service</h3>
+<h3 id="finding-and-using-a-factory-service">Finding and using a Factory service<a class="headerlink" href="#finding-and-using-a-factory-service" title="Permanent link">&para;</a></h3>
 <p>Let's imagine you have the following class:</p>
 <div class="codehilite"><pre><span class="nd">@Component</span><span class="o">(</span><span class="n">name</span><span class="o">=</span><span class="s">&quot;my-factory&quot;</span><span class="o">)</span>
 <span class="kd">public</span> <span class="kd">class</span> <span class="nc">MyImplementation</span> <span class="o">{</span>
@@ -223,7 +234,7 @@
 
 
 <p>When no name is provided (in the <code>@Component</code> annotation), the qualified class name is used as factory name.</p>
-<h3 id="retrieving-factory-information">Retrieving factory information</h3>
+<h3 id="retrieving-factory-information">Retrieving factory information<a class="headerlink" href="#retrieving-factory-information" title="Permanent link">&para;</a></h3>
 <p>Once you have the <code>factory</code> object, you can get a couple of additional metadata. The factory name can be retrieved with <code>getName</code>. Additionally, the factory version is retrieved with the <code>getVersion</code> method.</p>
 <p>The current factory state is accessible with the <code>getState</code> method. A factory can either be <code>VALID</code> or <code>INVALID</code>. A factory is valid only and only if all the required <em>handlers</em> are available (don't worry, you don't really need to know this definition). In other words, when a factory is not valid, it just means that a <em>handler</em> is not there (the bundle is not deployed).</p>
 <p>By using the <code>getComponentDescription()</code> method, you can retrieve additional information about the factory. Check the <a href="http://felix.apache.org/ipojo/api/1.12.1/org/apache/felix/ipojo/architecture/ComponentTypeDescription.html">ComponentTypeDescription 
@@ -242,7 +253,7 @@ API</a> for more information.</p>
 </pre></div>
 
 
-<h3 id="creating-an-instance">Creating an instance</h3>
+<h3 id="creating-an-instance">Creating an instance<a class="headerlink" href="#creating-an-instance" title="Permanent link">&para;</a></h3>
 <p>Factory services are generally used to create instances. The <code>createComponentInstance</code> method let you create instances. It receives a configuration object (potentially <code>null</code>):</p>
 <div class="codehilite"><pre><span class="kd">public</span> <span class="kt">void</span> <span class="nf">createMyInstance</span><span class="o">()</span> <span class="kd">throws</span> <span class="n">Exception</span> <span class="o">{</span>
         <span class="n">ComponentInstance</span> <span class="n">instance</span> <span class="o">=</span> <span class="n">factory</span><span class="o">.</span><span class="na">createComponentInstance</span><span class="o">(</span><span class="kc">null</span><span class="o">);</span> 
@@ -263,7 +274,7 @@ API</a> for more information.</p>
 
 <p>}</p>
 <p>To give a name to your instance, set the <code>instance.name</code> property.</p>
-<h3 id="getting-created-instances">Getting created instances</h3>
+<h3 id="getting-created-instances">Getting created instances<a class="headerlink" href="#getting-created-instances" title="Permanent link">&para;</a></h3>
 <p>The Factory service also allows you to retrieve the created instances:</p>
 <div class="codehilite"><pre><span class="kd">public</span> <span class="kt">void</span> <span class="nf">listInstancesFromFactory</span><span class="o">(</span><span class="n">Factory</span> <span class="n">factory</span><span class="o">)</span> <span class="o">{</span>
     <span class="k">for</span> <span class="o">(</span><span class="n">ComponentInstance</span> <span class="n">instance</span> <span class="o">:</span> <span class="n">factory</span><span class="o">.</span><span class="na">getInstances</span><span class="o">())</span> <span class="o">{</span>
@@ -273,11 +284,11 @@ API</a> for more information.</p>
 </pre></div>
 
 
-<h3 id="deleting-instances">Deleting instances</h3>
+<h3 id="deleting-instances">Deleting instances<a class="headerlink" href="#deleting-instances" title="Permanent link">&para;</a></h3>
 <p>You can't delete an instance directly from the factory object. However, you can from the <code>ComponentInstance</code> object. In the case you already have this object, just call the <code>dispose()</code> method. Otherwise, retrieve the component instance from the factory object and then call the <code>dispose()</code> method.</p>
-<h3 id="observing-the-factory-state">Observing the factory state</h3>
+<h3 id="observing-the-factory-state">Observing the factory state<a class="headerlink" href="#observing-the-factory-state" title="Permanent link">&para;</a></h3>
 <p>As stated above, factory objects have a state. We already saw how to retrieve the current state of the factory. You can also register a <a href="http://felix.apache.org/ipojo/api/1.12.1/org/apache/felix/ipojo/architecture/FactoryStateListener.html">FactoryStateListener</a> to be notified when the state changes. The methods <code>addFactoryStateListener</code> and <code>removeFactoryStateListener</code> let you respectively register and unregister the listener.</p>
-<h2 id="declaration-publication-vs-programmatic-creation">Declaration publication vs. Programmatic creation</h2>
+<h2 id="declaration-publication-vs-programmatic-creation">Declaration publication vs. Programmatic creation<a class="headerlink" href="#declaration-publication-vs-programmatic-creation" title="Permanent link">&para;</a></h2>
 <p>This page has explained how to create an instance from the Factory service. However, when the factory leaves or become invalid your instance is disposed. The instance is <strong>not</strong> recreated when the factory comes back or is revalidated.</p>
 <p>To avoid to have to listen and manage these events, you can use an <a href="http://felix.apache.org/ipojo/api/1.12.1/org/apache/felix/ipojo/architecture/InstanceDeclaration.html">InstanceDeclaration</a>.
 An instance declaration is a service you publish to instruct iPOJO to create an instance

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/ipojo-advanced-topics/service-binding-interceptors.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/ipojo-advanced-topics/service-binding-interceptors.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/ipojo-advanced-topics/service-binding-interceptors.html Wed Nov  4 07:43:11 2015
@@ -171,7 +171,18 @@
 
     <div class="container">
         <div class="content">
-            <h1 id="service-binding-interceptors">Service Binding Interceptors</h1>
+            <style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="service-binding-interceptors">Service Binding Interceptors<a class="headerlink" href="#service-binding-interceptors" title="Permanent link">&para;</a></h1>
 <p>Service Bindings are the connection between a service consumer and a service provider. Following the service-orientation paradigm (<em>publication-lookup-binding</em>), bindings are woven based a <em>local</em> analysis only: the consumer tracks and chooses the service to user. However, this <em>locality</em> avoids using more global knowledge to resolve the dependencies.</p>
 <p>Service binding interceptors allows you to customize the service bindings from outside the involved components (providers or consumers). It let you adapt the bindings dynamically without touching anything in your component implementation.</p>
 <div class="toc">
@@ -187,7 +198,7 @@
 </li>
 </ul>
 </div>
-<h2 id="whats-an-interceptor">What's an interceptor</h2>
+<h2 id="whats-an-interceptor">What's an interceptor<a class="headerlink" href="#whats-an-interceptor" title="Permanent link">&para;</a></h2>
 <p>Interceptors are services exposed in the OSGi service registry. They can be iPOJO components, but it's not a necessity. </p>
 <p>Each interceptor can manage a set of dependencies. The interceptor selects this set with a LDAP filter, exposed as service properties (named <code>target</code>):</p>
 <div class="codehilite"><pre><span class="nd">@Component</span><span class="o">(</span><span class="n">immediate</span> <span class="o">=</span> <span class="kc">true</span><span class="o">)</span>
@@ -210,14 +221,14 @@
 <li><a href="http://felix.apache.org/ipojo/api/1.12.1/org/apache/felix/ipojo/dependency/interceptors/ServiceBindingInterceptor.html">Binding interceptors</a> - can modify the injected service objects</li>
 </ul>
 <p>For all these classes, default implementations are available in (http://felix.apache.org/ipojo/api/1.12.1/org/apache/felix/ipojo/dependency/interceptors/package-summary.html).</p>
-<h2 id="service-dependency-theory">Service dependency theory</h2>
+<h2 id="service-dependency-theory">Service dependency theory<a class="headerlink" href="#service-dependency-theory" title="Permanent link">&para;</a></h2>
 <p>Before looking more deeply into these interceptors, let's first explain the service dependency principle. Before being injected inside the component's code, a service (reference) traverses a set of layers. The service dependencies consider all services from the service registry and narrows this set to select the right set of services. The narrowing process has three phases.</p>
 <p>The initial set of services considered by the service dependencies is named <em>base set</em>. It contains all services from the service registry providing the requested service interface.</p>
 <p>Then, for all services from the base set, the tracking interceptors (handling the service dependency) can decide whether or not to accept the service. By this way, they can decide to hide services. They are also able to <em>transform</em> services, to add and/or remove service properties. Several tracking interceptors can handle the same service dependency. They are invoked sequentially. Service accepted by all tracking interceptors are composed the <em>matching set</em>. Notice that the OSGi LDAP filters are tracking interceptors.</p>
 <p><img src="narrowing.png"/></p>
 <p>Unlike service tracking interceptors, only one ranking interceptor can be plugged on a service dependency. The ranking interceptor transforms the matching set to the <em>selected set</em> by selecting and sorting services. The iPOJO comparator feature is a ranking interceptor. Notice that ranking interceptor may select an empty set from the matching set. </p>
 <p>Finally, the last layer is the binding interceptor. This layer does not narrow the service set, but may interceptor the <em>weaving</em> of the binding for monitoring or interception purposes.</p>
-<h2 id="selection-of-service-dependencies">Selection of service dependencies</h2>
+<h2 id="selection-of-service-dependencies">Selection of service dependencies<a class="headerlink" href="#selection-of-service-dependencies" title="Permanent link">&para;</a></h2>
 <p>All interceptors must publish a <em>target</em> service property indicating the set of service dependency they handle. This property is an LDAP filter that can rely on the following properties:</p>
 <ul>
 <li><em>instance.name</em> : to select all dependencies of a specific instance (String)</li>
@@ -239,7 +250,7 @@
 <code>(&amp;(instance.name=instance)(dependency.id=foo))</code></li>
 <li>select all dependencies targeting <code>AbstractService</code> or sub-classes: <code>(objectClass=o.o…AbstractService)</code></li>
 </ul>
-<h2 id="service-tracking-interceptors">Service Tracking Interceptors</h2>
+<h2 id="service-tracking-interceptors">Service Tracking Interceptors<a class="headerlink" href="#service-tracking-interceptors" title="Permanent link">&para;</a></h2>
 <p>Service tracking interceptors are responsible for accepting matching services. Their main goal is to filter the <em>base set</em>. The following tracking interceptor hides all services with the <code>hidden</code> property:</p>
 <div class="codehilite"><pre><span class="nd">@Component</span><span class="o">(</span><span class="n">immediate</span> <span class="o">=</span> <span class="kc">true</span><span class="o">)</span>
 <span class="nd">@Provides</span>
@@ -288,7 +299,7 @@
 
 <p>The <code>invalidateMatchingServices</code> invalidates the matching service set and triggers a complete evaluation of the base set.</p>
 <p>Several tracking interceptors can manage the same dependency. All interceptors must accept matching services. The last evaluated tracking interceptor is the iPOJO LDAP filter.</p>
-<h2 id="service-ranking-interceptors">Service Ranking Interceptors</h2>
+<h2 id="service-ranking-interceptors">Service Ranking Interceptors<a class="headerlink" href="#service-ranking-interceptors" title="Permanent link">&para;</a></h2>
 <p>Service Ranking Interceptors receive the services from the matching set as input and returns a sorted sub-set. Unlike service tracking interceptors, only one ranking interceptor can manage a dependency.</p>
 <div class="codehilite"><pre><span class="nd">@Component</span><span class="o">(</span><span class="n">immediate</span> <span class="o">=</span> <span class="kc">true</span><span class="o">)</span>
 <span class="nd">@Provides</span>
@@ -331,7 +342,7 @@
 
 
 <p>The iPOJO comparator is a ranking interceptor. As only one interceptor can manage the dependency, the comparator is replaced when an external interceptor is plugged. It is restored when the external interceptors disappears.</p>
-<h2 id="binding-service-interceptors">Binding Service Interceptors</h2>
+<h2 id="binding-service-interceptors">Binding Service Interceptors<a class="headerlink" href="#binding-service-interceptors" title="Permanent link">&para;</a></h2>
 <p>The last category of interceptors is bindings interceptors. They intercepts the binding weaving, and thus, can <em>change</em> the injected service objects. This kind of interceptors are often used to inject a proxy intercepting some invocations:</p>
 <div class="codehilite"><pre><span class="nd">@Component</span>
 <span class="nd">@Provides</span>

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/ipojo-news.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/ipojo-news.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/ipojo-news.html Wed Nov  4 07:43:11 2015
@@ -171,7 +171,18 @@
 
     <div class="container">
         <div class="content">
-            <h1 id="whats-hot">What's hot ?</h1>
+            <style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="whats-hot">What's hot ?<a class="headerlink" href="#whats-hot" title="Permanent link">&para;</a></h1>
 <ul>
 <li><em>iPOJO Manipulator (1.12.1) and Runtime (1.12.1)</em> are now available in the <a href="http://felix.apache.org/downloads.cgi">downloads</a> section and from the Maven repository. (December 24, 2014)</li>
 <li><em>iPOJO Manipulator (1.12.0) and Runtime (1.12.0)</em> are now available in the <a href="http://felix.apache.org/downloads.cgi">downloads</a> section and from the Maven repository. (May 17, 2014)</li>

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-jaas.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-jaas.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-jaas.html Wed Nov  4 07:43:11 2015
@@ -39,17 +39,28 @@
     </div>
     
     <div class="menu"> 
-      <p><a href="/news.html">news</a>  <br />
-<a href="/license.html">license</a>  <br />
-<a href="/downloads.cgi">downloads</a>  <br />
-<a href="/documentation.html">documentation</a>  <br />
-<a href="/mailinglists.html">mailing lists</a>  <br />
-<a href="/documentation/community/contributing.html">contributing</a>  <br />
-<a href="/sitemap.html">site map</a>  <br />
-<a href="http://www.apache.org/">asf</a>  <br />
-<a href="http://www.apache.org/security/">security</a>  <br />
-<a href="http://www.apache.org/foundation/sponsorship.html">sponsorship</a>  <br />
-<a href="http://www.apache.org/foundation/thanks.html">sponsors</a>    </p>
+      <style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p><a href="/news.html">News</a>  <br />
+<a href="/license.html">License</a>  <br />
+<a href="/downloads.cgi">Downloads</a>  <br />
+<a href="/documentation.html">Documentation</a>  <br />
+<a href="/mailinglists.html">Mailing Lists</a>  <br />
+<a href="/documentation/community/contributing.html">Contributing</a>  <br />
+<a href="/sitemap.html">Site Map</a>  <br />
+<a href="http://www.apache.org/">ASF</a>  <br />
+<a href="http://www.apache.org/security/">Security</a>  <br />
+<a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a>  <br />
+<a href="http://www.apache.org/foundation/thanks.html">Sponsors</a>    </p>
 <iframe
     src="http://www.apache.org/ads/button.html"
     style="border-width:0; float: left"
@@ -67,6 +78,17 @@
 
       <h1>Apache Felix JAAS Support</h1>
       <style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<style type="text/css">
 img {
  width:auto;
 }
@@ -89,10 +111,10 @@ img {
 <li><a href="#logincontextfactory-mode">LoginContextFactory Mode</a></li>
 <li><a href="#configuration-spi-with-default-policy-mode">Configuration SPI with Default Policy Mode</a></li>
 <li><a href="#replace-global-configuration-mode">Replace Global Configuration Mode</a></li>
-<li><a href="#wzxhzdk10wzxhzdk11modified-boot-classpath-mode"><a name="boot-classpath"></a>Modified Boot Classpath Mode</a></li>
+<li><a href="#modified-boot-classpath-mode"><a name="boot-classpath"></a>Modified Boot Classpath Mode</a></li>
 </ul>
 </li>
-<li><a href="#wzxhzdk12wzxhzdk13jaas-configuration-spi-settings"><a name="configuration-spi"></a>JAAS Configuration SPI Settings</a></li>
+<li><a href="#jaas-configuration-spi-settings"><a name="configuration-spi"></a>JAAS Configuration SPI Settings</a></li>
 </ul>
 </li>
 <li><a href="#webconsole-plugin">WebConsole Plugin</a></li>
@@ -110,7 +132,7 @@ img {
 <li>It works well with the dynamic nature of the OSGi env</li>
 <li>Implementation depends only on Core OSGi API and ConfigAdmin (RFC 104)</li>
 </ol>
-<h2 id="the-problem">The Problem</h2>
+<h2 id="the-problem">The Problem<a class="headerlink" href="#the-problem" title="Permanent link">&para;</a></h2>
 <p>The basic problem when using JAAS in OSGi is that it creates the LoginModule instance using reflection. This poses
 problem in OSGi env as the client bundle does not have the visibility of all the required LoginModule classes.</p>
 <p>A typical use of JAAS login looks like below</p>
@@ -131,7 +153,7 @@ to create the instance. This approach fa
 <li>Even if an implementation class was exported, importing this class in a consumer bundle would bind it to the specific
    implementation package provided, which violates the principle of loose coupling.</li>
 </ol>
-<h2 id="usage">Usage</h2>
+<h2 id="usage">Usage<a class="headerlink" href="#usage" title="Permanent link">&para;</a></h2>
 <p>The JAAS support involves following parts</p>
 <ol>
 <li>LoginModule Registration - Mechanism by which LoginModule is registered with a given <code>realm</code>.</li>
@@ -139,25 +161,25 @@ to create the instance. This approach fa
 </ol>
 <p>In section below we would first provide details on various ways by which a <code>LoginModule</code> would be configured so that
 it can participate in JAAS flow and then about various ways in which the client code can invoke the JAAS logic</p>
-<h3 id="loginmodule-registration">LoginModule registration</h3>
+<h3 id="loginmodule-registration">LoginModule registration<a class="headerlink" href="#loginmodule-registration" title="Permanent link">&para;</a></h3>
 <p>The login modules can be registered via two mechanism</p>
 <ul>
 <li>OSGi Configuration - LoginModule are registered via OSGi configuration</li>
 <li>LoginModuleFactory - LoginModule are registered with the OSGi ServiceRegistry via <code>LoginModuleFactory</code></li>
 </ul>
-<h4 id="a-osgi-configuration">A - OSGi Configuration</h4>
+<h4 id="a-osgi-configuration">A - OSGi Configuration<a class="headerlink" href="#a-osgi-configuration" title="Permanent link">&para;</a></h4>
 <p>LoginModules can also be configured via configuration which is somewhat similar to the file based configuration. It consist of two parts</p>
 <ul>
 <li>Information around which bundle provides a specific LoginModule module</li>
 <li>Configuration required to be passed to that LoginModule</li>
 </ul>
-<h5 id="manifest-header-entry">Manifest Header Entry</h5>
+<h5 id="manifest-header-entry">Manifest Header Entry<a class="headerlink" href="#manifest-header-entry" title="Permanent link">&para;</a></h5>
 <p>Any bundle which provides a LoginModule class needs to provide this information via <em>Jaas-ModuleClass</em> manifest header.</p>
 <div class="codehilite"><pre><span class="nt">&lt;Jaas-ModuleClass&gt;</span>org.apache.felix.example.jaas.config.internal.SampleConfigLoginModule<span class="nt">&lt;/Jaas-ModuleClass&gt;</span>
 </pre></div>
 
 
-<h5 id="configuration">Configuration</h5>
+<h5 id="configuration">Configuration<a class="headerlink" href="#configuration" title="Permanent link">&para;</a></h5>
 <p>JAAS module depends on OSGi Configuration for managing the LoginModule configuration. The configuration factory PID is
 <code>org.apache.felix.jaas.Configuration.factory</code>.It provides the required metatype descriptor thus enabling configuration
 via "Configuration" tab of Felix WebConsole</p>
@@ -172,7 +194,7 @@ via "Configuration" tab of Felix WebCons
    in a descending order (i.e. higher value ranked configurations come first)</li>
 </ul>
 <p>For an example refer to <a href="http://svn.apache.org/repos/asf/felix/trunk/examples/jaas/launcher/src/main/config/org.apache.felix.jaas.Configuration.factory-simple.cfg">Sample Configuration</a>. It configures a SampleConfigLoginModule for <code>sample</code> realm</p>
-<h4 id="b-loginmodulefactory">B - LoginModuleFactory</h4>
+<h4 id="b-loginmodulefactory">B - LoginModuleFactory<a class="headerlink" href="#b-loginmodulefactory" title="Permanent link">&para;</a></h4>
 <p>Any bundle which want to provide a LoginModule implementation would need to provide a factory service which implements the
 <a href="http://svn.apache.org/repos/asf/felix/trunk/jaas/src/main/java/org/apache/felix/jaas/LoginModuleFactory.java">LoginModuleFactory</a> interface. The factory needs to be registeredwith following optional properties</p>
 <ul>
@@ -216,9 +238,9 @@ via "Configuration" tab of Felix WebCons
 
 <p>Refer to <a href="http://svn.apache.org/repos/asf/felix/trunk/examples/jaas/lm-jdbc/src/main/java/org/apache/felix/example/jaas/jdbc/JdbcLoginModuleFactory.java">JdbcLoginModuleFactory</a> for one example of its usage. It constructs a JdbcLoginModule based on the
 configuration and passes on the datasource.</p>
-<h3 id="logincontext-creation-patterns">LoginContext creation patterns</h3>
+<h3 id="logincontext-creation-patterns">LoginContext creation patterns<a class="headerlink" href="#logincontext-creation-patterns" title="Permanent link">&para;</a></h3>
 <p>There are various ways through which a JAAS Client can invoke the JAAS login.</p>
-<h4 id="logincontextfactory-mode">LoginContextFactory Mode</h4>
+<h4 id="logincontextfactory-mode">LoginContextFactory Mode<a class="headerlink" href="#logincontextfactory-mode" title="Permanent link">&para;</a></h4>
 <p>In this mode the client logic obtains a reference to the <code>org.apache.felix.jaas.LoginContextFactory</code> service
 and then creates a <code>LoginContext</code> instance</p>
 <div class="codehilite"><pre><span class="p">:</span><span class="n">java</span>
@@ -244,7 +266,7 @@ and then creates a <code>LoginContext</c
 <li>No need to manage Thread Context Classloader while invoking <code>LoginContext</code></li>
 <li>No need to import LoginModule related packages</li>
 </ul>
-<h4 id="configuration-spi-with-default-policy-mode">Configuration SPI with Default Policy Mode</h4>
+<h4 id="configuration-spi-with-default-policy-mode">Configuration SPI with Default Policy Mode<a class="headerlink" href="#configuration-spi-with-default-policy-mode" title="Permanent link">&para;</a></h4>
 <p>In this mode the client logic explicitly fetch the JAAS Configuration and then pass it on to the LoginContext. In this
 mode the <a href="#configuration-spi">JAAS Configuration Policy</a> is set to <code>Default</code>.</p>
 <div class="codehilite"><pre><span class="n">CallbackHandler</span> <span class="n">handler</span> <span class="o">=</span> <span class="o">...;</span>
@@ -279,7 +301,7 @@ mode the <a href="#configuration-spi">JA
   Refer to <a href="#boot-classpath">Boot classpath</a> section for more details</li>
 <li>Global configuration is not modified so other users of JAAS are not affected</li>
 </ul>
-<h4 id="replace-global-configuration-mode">Replace Global Configuration Mode</h4>
+<h4 id="replace-global-configuration-mode">Replace Global Configuration Mode<a class="headerlink" href="#replace-global-configuration-mode" title="Permanent link">&para;</a></h4>
 <p>In this mode the JAAS bundle would replace the Global configuration through Configuration.setConfiguration call. In this
 mode the client code would use the normal LoginContext creation and the <a href="#configuration-spi">JAAS Configuration Policy</a>
 is set to <code>Replace Global Configuration</code>.</p>
@@ -307,7 +329,7 @@ is set to <code>Replace Global Configura
 <li>Global configuration is modified. So it might cause issue while running in co deployed scenarios like Application Server.</li>
 </ul>
 <p>Refer to <a href="http://svn.apache.org/repos/asf/felix/trunk/examples/jaas/app/src/main/java/org/apache/felix/example/jaas/app/internal/GlobalConfigDemoServlet.java">GlobalConfigDemoServlet</a> for an example</p>
-<h4 id="wzxhzdk10wzxhzdk11modified-boot-classpath-mode"><a name="boot-classpath"></a>Modified Boot Classpath Mode</h4>
+<h4 id="modified-boot-classpath-mode"><a name="boot-classpath"></a>Modified Boot Classpath Mode<a class="headerlink" href="#modified-boot-classpath-mode" title="Permanent link">&para;</a></h4>
 <p>In previous modes (except the LoginContextFactory mode) the client code needs to switch the Thread Context Classloader (TCCL).
 This is due the way JAAS logic instantiates the <code>LoginModule</code>. The Felix JAAS Support provides a <code>ProxyLoginModule</code> which
 takes care of routing the LoginModule calls properly. However for this class to be visible to JAAS logic one of the
@@ -316,9 +338,7 @@ two approaches can be used</p>
 <p>The client bundle  would need to</p>
 <ol>
 <li>Have an explicit import for <code>org.apache.felix.jaas.boot</code> package and</li>
-<li>
-<p>Manage TCCL explicitly which making JAAS related calls.</p>
-<div class="codehilite"><pre><span class="kd">final</span> <span class="n">Thread</span> <span class="n">current</span> <span class="o">=</span> <span class="n">Thread</span><span class="o">.</span><span class="na">currentThread</span><span class="o">();</span>
+<li>Manage TCCL explicitly which making JAAS related calls.<div class="codehilite"><pre><span class="kd">final</span> <span class="n">Thread</span> <span class="n">current</span> <span class="o">=</span> <span class="n">Thread</span><span class="o">.</span><span class="na">currentThread</span><span class="o">();</span>
 <span class="kd">final</span> <span class="n">ClassLoader</span> <span class="n">orig</span> <span class="o">=</span> <span class="n">current</span><span class="o">.</span><span class="na">getContextClassLoader</span><span class="o">();</span>
 <span class="k">try</span> <span class="o">{</span>
   <span class="n">current</span><span class="o">.</span><span class="na">setContextClassLoader</span><span class="o">(</span><span class="n">getClass</span><span class="o">().</span><span class="na">getClassLoader</span><span class="o">());</span>
@@ -336,9 +356,7 @@ two approaches can be used</p>
 <p>Another way would involve modifying the boot classpath.</p>
 <ol>
 <li>Place the <code>org.apache.felix.jaas-xxx-boot.jar</code> in the boot classpath via <code>-Xbootclasspath:bootclasspath</code> option</li>
-<li>
-<p>Make the <code>org.apache.felix.jaas.boot</code> part of boot delegation list</p>
-<div class="codehilite"><pre><span class="n">LoginContext</span> <span class="n">lc</span> <span class="o">=</span> <span class="k">new</span> <span class="n">LoginContext</span><span class="o">(</span><span class="s">&quot;sample&quot;</span><span class="o">,</span> <span class="n">subject</span><span class="o">,</span> <span class="n">handler</span><span class="o">);</span>
+<li>Make the <code>org.apache.felix.jaas.boot</code> part of boot delegation list<div class="codehilite"><pre><span class="n">LoginContext</span> <span class="n">lc</span> <span class="o">=</span> <span class="k">new</span> <span class="n">LoginContext</span><span class="o">(</span><span class="s">&quot;sample&quot;</span><span class="o">,</span> <span class="n">subject</span><span class="o">,</span> <span class="n">handler</span><span class="o">);</span>
 <span class="n">lc</span><span class="o">.</span><span class="na">login</span><span class="o">();</span>
 </pre></div>
 
@@ -347,7 +365,7 @@ two approaches can be used</p>
 </ol>
 <p>Note that in above code we do not have to manage TCCL and neither add an import to <code>org.apache.felix.jaas.boot</code> package</p>
 <p>Refer to <a href="http://svn.apache.org/repos/asf/felix/trunk/examples/jaas/app/src/main/java/org/apache/felix/example/jaas/app/internal/BootClasspathDemoServlet.java">BootClasspathDemoServlet</a> for code sample</p>
-<h3 id="wzxhzdk12wzxhzdk13jaas-configuration-spi-settings"><a name="configuration-spi"></a>JAAS Configuration SPI Settings</h3>
+<h3 id="jaas-configuration-spi-settings"><a name="configuration-spi"></a>JAAS Configuration SPI Settings<a class="headerlink" href="#jaas-configuration-spi-settings" title="Permanent link">&para;</a></h3>
 <p>There are various ways in which LoginContext can be created depending on the usage mode. The JAAS support exposes
 following properties</p>
 <p><img src="jaas-spi-config.png" align="center" /></p>
@@ -365,10 +383,10 @@ following properties</p>
 </ul>
 </li>
 </ul>
-<h2 id="webconsole-plugin">WebConsole Plugin</h2>
+<h2 id="webconsole-plugin">WebConsole Plugin<a class="headerlink" href="#webconsole-plugin" title="Permanent link">&para;</a></h2>
 <p>The runtime JAAS realm is exposed via a WebConsole Plugin.</p>
 <p><img src="jaas-plugin.png" align="center"/></p>
-<h2 id="resources">Resources</h2>
+<h2 id="resources">Resources<a class="headerlink" href="#resources" title="Permanent link">&para;</a></h2>
 <ol>
 <li><a href="http://docs.oracle.com/javase/1.5.0/docs/guide/security/jaas/JAASRefGuide.html">Java JAAS Reference Guide</a></li>
 <li><a href="http://docs.oracle.com/javase/1.5.0/docs/guide/security/jaas/tutorials/LoginConfigFile.html">JAAS Login Configuration File</a></li>

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-lightweight-http-service.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-lightweight-http-service.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-lightweight-http-service.html Wed Nov  4 07:43:11 2015
@@ -50,17 +50,17 @@
   visibility: hidden;
 }
 h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
-<p><a href="/news.html">news</a>  <br />
-<a href="/license.html">license</a>  <br />
-<a href="/downloads.cgi">downloads</a>  <br />
-<a href="/documentation.html">documentation</a>  <br />
-<a href="/mailinglists.html">mailing lists</a>  <br />
-<a href="/documentation/community/contributing.html">contributing</a>  <br />
-<a href="/sitemap.html">site map</a>  <br />
-<a href="http://www.apache.org/">asf</a>  <br />
-<a href="http://www.apache.org/security/">security</a>  <br />
-<a href="http://www.apache.org/foundation/sponsorship.html">sponsorship</a>  <br />
-<a href="http://www.apache.org/foundation/thanks.html">sponsors</a>    </p>
+<p><a href="/news.html">News</a>  <br />
+<a href="/license.html">License</a>  <br />
+<a href="/downloads.cgi">Downloads</a>  <br />
+<a href="/documentation.html">Documentation</a>  <br />
+<a href="/mailinglists.html">Mailing Lists</a>  <br />
+<a href="/documentation/community/contributing.html">Contributing</a>  <br />
+<a href="/sitemap.html">Site Map</a>  <br />
+<a href="http://www.apache.org/">ASF</a>  <br />
+<a href="http://www.apache.org/security/">Security</a>  <br />
+<a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a>  <br />
+<a href="http://www.apache.org/foundation/thanks.html">Sponsors</a>    </p>
 <iframe
     src="http://www.apache.org/ads/button.html"
     style="border-width:0; float: left"

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-log.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-log.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-log.html Wed Nov  4 07:43:11 2015
@@ -50,17 +50,17 @@
   visibility: hidden;
 }
 h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
-<p><a href="/news.html">news</a>  <br />
-<a href="/license.html">license</a>  <br />
-<a href="/downloads.cgi">downloads</a>  <br />
-<a href="/documentation.html">documentation</a>  <br />
-<a href="/mailinglists.html">mailing lists</a>  <br />
-<a href="/documentation/community/contributing.html">contributing</a>  <br />
-<a href="/sitemap.html">site map</a>  <br />
-<a href="http://www.apache.org/">asf</a>  <br />
-<a href="http://www.apache.org/security/">security</a>  <br />
-<a href="http://www.apache.org/foundation/sponsorship.html">sponsorship</a>  <br />
-<a href="http://www.apache.org/foundation/thanks.html">sponsors</a>    </p>
+<p><a href="/news.html">News</a>  <br />
+<a href="/license.html">License</a>  <br />
+<a href="/downloads.cgi">Downloads</a>  <br />
+<a href="/documentation.html">Documentation</a>  <br />
+<a href="/mailinglists.html">Mailing Lists</a>  <br />
+<a href="/documentation/community/contributing.html">Contributing</a>  <br />
+<a href="/sitemap.html">Site Map</a>  <br />
+<a href="http://www.apache.org/">ASF</a>  <br />
+<a href="http://www.apache.org/security/">Security</a>  <br />
+<a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a>  <br />
+<a href="http://www.apache.org/foundation/thanks.html">Sponsors</a>    </p>
 <iframe
     src="http://www.apache.org/ads/button.html"
     style="border-width:0; float: left"

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-manifest-generator-mangen.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-manifest-generator-mangen.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-manifest-generator-mangen.html Wed Nov  4 07:43:11 2015
@@ -50,17 +50,17 @@
   visibility: hidden;
 }
 h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
-<p><a href="/news.html">news</a>  <br />
-<a href="/license.html">license</a>  <br />
-<a href="/downloads.cgi">downloads</a>  <br />
-<a href="/documentation.html">documentation</a>  <br />
-<a href="/mailinglists.html">mailing lists</a>  <br />
-<a href="/documentation/community/contributing.html">contributing</a>  <br />
-<a href="/sitemap.html">site map</a>  <br />
-<a href="http://www.apache.org/">asf</a>  <br />
-<a href="http://www.apache.org/security/">security</a>  <br />
-<a href="http://www.apache.org/foundation/sponsorship.html">sponsorship</a>  <br />
-<a href="http://www.apache.org/foundation/thanks.html">sponsors</a>    </p>
+<p><a href="/news.html">News</a>  <br />
+<a href="/license.html">License</a>  <br />
+<a href="/downloads.cgi">Downloads</a>  <br />
+<a href="/documentation.html">Documentation</a>  <br />
+<a href="/mailinglists.html">Mailing Lists</a>  <br />
+<a href="/documentation/community/contributing.html">Contributing</a>  <br />
+<a href="/sitemap.html">Site Map</a>  <br />
+<a href="http://www.apache.org/">ASF</a>  <br />
+<a href="http://www.apache.org/security/">Security</a>  <br />
+<a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a>  <br />
+<a href="http://www.apache.org/foundation/thanks.html">Sponsors</a>    </p>
 <iframe
     src="http://www.apache.org/ads/button.html"
     style="border-width:0; float: left"

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-maven-bundle-plugin-bnd.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-maven-bundle-plugin-bnd.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-maven-bundle-plugin-bnd.html Wed Nov  4 07:43:11 2015
@@ -50,17 +50,17 @@
   visibility: hidden;
 }
 h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
-<p><a href="/news.html">news</a>  <br />
-<a href="/license.html">license</a>  <br />
-<a href="/downloads.cgi">downloads</a>  <br />
-<a href="/documentation.html">documentation</a>  <br />
-<a href="/mailinglists.html">mailing lists</a>  <br />
-<a href="/documentation/community/contributing.html">contributing</a>  <br />
-<a href="/sitemap.html">site map</a>  <br />
-<a href="http://www.apache.org/">asf</a>  <br />
-<a href="http://www.apache.org/security/">security</a>  <br />
-<a href="http://www.apache.org/foundation/sponsorship.html">sponsorship</a>  <br />
-<a href="http://www.apache.org/foundation/thanks.html">sponsors</a>    </p>
+<p><a href="/news.html">News</a>  <br />
+<a href="/license.html">License</a>  <br />
+<a href="/downloads.cgi">Downloads</a>  <br />
+<a href="/documentation.html">Documentation</a>  <br />
+<a href="/mailinglists.html">Mailing Lists</a>  <br />
+<a href="/documentation/community/contributing.html">Contributing</a>  <br />
+<a href="/sitemap.html">Site Map</a>  <br />
+<a href="http://www.apache.org/">ASF</a>  <br />
+<a href="http://www.apache.org/security/">Security</a>  <br />
+<a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a>  <br />
+<a href="http://www.apache.org/foundation/thanks.html">Sponsors</a>    </p>
 <iframe
     src="http://www.apache.org/ads/button.html"
     style="border-width:0; float: left"

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-maven-obr-plugin.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-maven-obr-plugin.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-maven-obr-plugin.html Wed Nov  4 07:43:11 2015
@@ -50,17 +50,17 @@
   visibility: hidden;
 }
 h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
-<p><a href="/news.html">news</a>  <br />
-<a href="/license.html">license</a>  <br />
-<a href="/downloads.cgi">downloads</a>  <br />
-<a href="/documentation.html">documentation</a>  <br />
-<a href="/mailinglists.html">mailing lists</a>  <br />
-<a href="/documentation/community/contributing.html">contributing</a>  <br />
-<a href="/sitemap.html">site map</a>  <br />
-<a href="http://www.apache.org/">asf</a>  <br />
-<a href="http://www.apache.org/security/">security</a>  <br />
-<a href="http://www.apache.org/foundation/sponsorship.html">sponsorship</a>  <br />
-<a href="http://www.apache.org/foundation/thanks.html">sponsors</a>    </p>
+<p><a href="/news.html">News</a>  <br />
+<a href="/license.html">License</a>  <br />
+<a href="/downloads.cgi">Downloads</a>  <br />
+<a href="/documentation.html">Documentation</a>  <br />
+<a href="/mailinglists.html">Mailing Lists</a>  <br />
+<a href="/documentation/community/contributing.html">Contributing</a>  <br />
+<a href="/sitemap.html">Site Map</a>  <br />
+<a href="http://www.apache.org/">ASF</a>  <br />
+<a href="http://www.apache.org/security/">Security</a>  <br />
+<a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a>  <br />
+<a href="http://www.apache.org/foundation/thanks.html">Sponsors</a>    </p>
 <iframe
     src="http://www.apache.org/ads/button.html"
     style="border-width:0; float: left"




Mime
View raw message