felix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r963800 [3/16] - in /websites/staging/felix/trunk/content: ./ documentation/ documentation/community/ documentation/development/ documentation/faqs/ documentation/subprojects/ documentation/subprojects/apache-felix-commons/ documentation/su...
Date Tue, 01 Sep 2015 06:05:20 GMT
Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-autoconf.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-autoconf.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-autoconf.html Tue Sep  1 06:05:17 2015
@@ -39,7 +39,18 @@
     </div>
     
     <div class="menu"> 
-      <p><a href="/news.html">news</a>  <br />
+      <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 />
@@ -66,10 +77,21 @@
       </div>
 
       <h1>Apache Felix Auto Configuration</h1>
-      <h1 id="apache-felix-auto-configuration">Apache Felix Auto Configuration</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="apache-felix-auto-configuration">Apache Felix Auto Configuration<a class="headerlink" href="#apache-felix-auto-configuration" title="Permanent link">&para;</a></h1>
 <p>This project implements the OSGi Auto Configuration specification; please consult the OSGi Compendium Specification chapter 115 for more information.</p>
       <div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
-        Rev. 1490041 by marrs on Wed, 5 Jun 2013 21:57:35 +0000
+        Rev. 1700393 by cziegeler on Tue, 1 Sep 2015 06:04:06 +0000
       </div>
       <div class="trademarkFooter"> 
         Apache Felix, Felix, Apache, the Apache feather logo, and the Apache Felix project

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-commons.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-commons.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-commons.html Tue Sep  1 06:05:17 2015
@@ -39,7 +39,18 @@
     </div>
     
     <div class="menu"> 
-      <p><a href="/news.html">news</a>  <br />
+      <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 />
@@ -66,12 +77,23 @@
       </div>
 
       <h1>Apache Felix Commons</h1>
-      <h3 id="purpose">Purpose</h3>
+      <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>
+<h3 id="purpose">Purpose<a class="headerlink" href="#purpose" title="Permanent link">&para;</a></h3>
 <p>Apache Felix Commons is a community effort to create OSGi bundle ("bundlized") versions of popular third-party open-source libraries.  Today, OSGi developers must create bundles out of third-party libraries within their own development communities.  The purpose of Felix Commons is to avoid duplicating the effort of bundle creation by sharing these bundlized artifacts.  Our hope is that over time, the original developers of the third-party libraries can use these bundlized libraries to learn how to add OSGi metadata to their project artifacts and to become comfortable with the overall non-invasive process.  Felix Commons is thus a large "project" of POMs where each bundle POM simply has a dependency on the library it wants to convert.  The Felix Maven Bundle Plugin will then convert the dependency automatically and the bundle will be available via existing Maven infrastructure.</p>
 <p>This web page will be used to document who is doing what and to provide pointers to more information.</p>
-<h3 id="how-can-i-help">How Can I Help?</h3>
+<h3 id="how-can-i-help">How Can I Help?<a class="headerlink" href="#how-can-i-help" title="Permanent link">&para;</a></h3>
 <p>If you have libraries you have turned into bundles, then you can offer to contribute them.  Additionally, you may request that a certain bundle be created.  If you wish to submit a POM file for a specific library, you can attach it to a <a href="http://issues.apache.org/jira/browse/Felix">Felix JIRA issue</a> under the "Felix Commons" component.  For Apache purposes, contributing a bundle POM is the same as contributing code.</p>
-<h3 id="getting-started">Getting Started</h3>
+<h3 id="getting-started">Getting Started<a class="headerlink" href="#getting-started" title="Permanent link">&para;</a></h3>
 <p>In most cases, creating bundlized versions of a library is as simple as creating a POM file for the library using Felix' new <a href="/documentation/subprojects/apache-felix-maven-bundle-plugin-bnd.html">Maven Bundle Plugin</a>.  The OSGi headers are non-intrusive.  A JAR can be made in such a way that it runs on the Classpath as well as a bundle in an OSGi framework.  In short you:
 1. Set the groupId to:</p>
 <div class="codehilite"><pre><span class="nt">&lt;groupId&gt;</span>org.apache.felix.commons<span class="nt">&lt;/groupId&gt;</span>
@@ -92,8 +114,8 @@
 </li>
 </ol>
 <p>We recommend you read the longer <a href="/documentation/subprojects/apache-felix-commons/creating-bundles-using-bnd.html">steps for converting a library to a bundle</a>.</p>
-<h3 id="contributions">Contributions</h3>
-<table>
+<h3 id="contributions">Contributions<a class="headerlink" href="#contributions" title="Permanent link">&para;</a></h3>
+<table class="table">
 <thead>
 <tr>
 <th>Library</th>
@@ -219,9 +241,9 @@
 </tr>
 </tbody>
 </table>
-<h3 id="supporting-libraries">Supporting Libraries</h3>
+<h3 id="supporting-libraries">Supporting Libraries<a class="headerlink" href="#supporting-libraries" title="Permanent link">&para;</a></h3>
 <p>These are projects that have expressed support for the Felix Commons initiative and that are working directly within their respective projects to support OSGi.</p>
-<table>
+<table class="table">
 <thead>
 <tr>
 <th>Project</th>
@@ -286,7 +308,7 @@
 <td></td>
 </tr>
 <tr>
-<td>{quote}</td>
+<td quote="quote"></td>
 <td></td>
 <td></td>
 <td></td>
@@ -298,7 +320,7 @@
 <td></td>
 </tr>
 <tr>
-<td>{quote}</td>
+<td quote="quote"></td>
 <td></td>
 <td></td>
 <td></td>
@@ -306,7 +328,7 @@
 </tbody>
 </table>
       <div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
-        Rev. 1422427 by fmeschbe on Sun, 16 Dec 2012 00:36:51 +0000
+        Rev. 1700393 by cziegeler on Tue, 1 Sep 2015 06:04:06 +0000
       </div>
       <div class="trademarkFooter"> 
         Apache Felix, Felix, Apache, the Apache feather logo, and the Apache Felix project

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-commons/creating-bundles-using-bnd.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-commons/creating-bundles-using-bnd.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-commons/creating-bundles-using-bnd.html Tue Sep  1 06:05:17 2015
@@ -39,7 +39,18 @@
     </div>
     
     <div class="menu"> 
-      <p><a href="/news.html">news</a>  <br />
+      <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 />
@@ -66,9 +77,20 @@
       </div>
 
       <h1>Creating Bundles Using BND</h1>
-      <h5 id="purpose">Purpose</h5>
+      <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>
+<h5 id="purpose">Purpose<a class="headerlink" href="#purpose" title="Permanent link">&para;</a></h5>
 <p>Provide the list of steps required to create a library bundle by wrapping the library jar using bnd (http://www.aqute.biz/Code/Bnd).</p>
-<h5 id="steps">Steps</h5>
+<h5 id="steps">Steps<a class="headerlink" href="#steps" title="Permanent link">&para;</a></h5>
 <ol>
 <li>Use bnd to analyze the library jar (e.g., java -jar bnd-0.0.jar print path/to/FOO.jar) </li>
 <li>At the bottom of the bnd output, look for "Unresolved references to ..." which identify package dependencies. If found, 
@@ -89,7 +111,7 @@
 <li>Use bnd to verify the bundle's contents (e.g., java -jar bnd-0.0.jar print target/FOO-osgi-VERSION.jar) </li>
 <li>Run "mvn install" to install the bundle in the local repository</li>
 </ol>
-<h5 id="example-pom">Example POM</h5>
+<h5 id="example-pom">Example POM<a class="headerlink" href="#example-pom" title="Permanent link">&para;</a></h5>
 <div class="codehilite"><pre><span class="nt">&lt;project</span>
   <span class="na">xmlns=</span><span class="s">&quot;http://maven.apache.org/POM/4.0.0&quot;</span>
   <span class="na">xmlns:xsi=</span><span class="s">&quot;http://www.w3.org/2001/XMLSchema-instance&quot;</span>
@@ -139,13 +161,13 @@
 </pre></div>
 
 
-<h5 id="resources">Resources</h5>
+<h5 id="resources">Resources<a class="headerlink" href="#resources" title="Permanent link">&para;</a></h5>
 <p>Bnd - Bundle Tool
 http://www.aqute.biz/Code/Bnd</p>
 <p>Bundle Plugin for Maven
 http://felix.apache.org/site/maven-bundle-plugin-bnd.html</p>
       <div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
-        Rev. 1422427 by fmeschbe on Sun, 16 Dec 2012 00:36:51 +0000
+        Rev. 1700393 by cziegeler on Tue, 1 Sep 2015 06:04:06 +0000
       </div>
       <div class="trademarkFooter"> 
         Apache Felix, Felix, Apache, the Apache feather logo, and the Apache Felix project

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-deployment-admin.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-deployment-admin.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-deployment-admin.html Tue Sep  1 06:05:17 2015
@@ -39,7 +39,18 @@
     </div>
     
     <div class="menu"> 
-      <p><a href="/news.html">news</a>  <br />
+      <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 />
@@ -66,10 +77,21 @@
       </div>
 
       <h1>Apache Felix Deployment Admin</h1>
-      <h1 id="apache-felix-deployment-admin">Apache Felix Deployment Admin</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="apache-felix-deployment-admin">Apache Felix Deployment Admin<a class="headerlink" href="#apache-felix-deployment-admin" title="Permanent link">&para;</a></h1>
 <p>This project implements the OSGi Deployment Admin specification; please consult the OSGi Compendium Specification chapter 114 for more information.</p>
       <div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
-        Rev. 1490041 by marrs on Wed, 5 Jun 2013 21:57:35 +0000
+        Rev. 1700393 by cziegeler on Tue, 1 Sep 2015 06:04:06 +0000
       </div>
       <div class="trademarkFooter"> 
         Apache Felix, Felix, Apache, the Apache feather logo, and the Apache Felix project

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-file-install.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-file-install.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-file-install.html Tue Sep  1 06:05:17 2015
@@ -39,7 +39,18 @@
     </div>
     
     <div class="menu"> 
-      <p><a href="/news.html">news</a>  <br />
+      <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 />
@@ -66,7 +77,18 @@
       </div>
 
       <h1>Apache Felix File Install</h1>
-      <h1 id="apache-felix-file-install">Apache Felix File Install</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="apache-felix-file-install">Apache Felix File Install<a class="headerlink" href="#apache-felix-file-install" title="Permanent link">&para;</a></h1>
 <p>File Install is a directory based OSGi management agent. It uses a directory in the file system to install and start a bundle when it is first placed there. It updates the bundle when you update the bundle file in the directory and, when the file is deleted, it will stop and uninstall the bundle.</p>
 <p>File Install can do the same for configuration configuration files. This surprisingly simple bundle is very powerful because there are so many programs that work with the file system. For example:</p>
 <ul>
@@ -74,9 +96,9 @@
 <li>You can download bundles from the web and directly install them without any extra effort.</li>
 <li>You can easily drag and drop bundles in and out of the framework.</li>
 </ul>
-<h2 id="setup">Setup</h2>
+<h2 id="setup">Setup<a class="headerlink" href="#setup" title="Permanent link">&para;</a></h2>
 <p>The bundle runs on any framework. For its configuration, it will use the following system properties:</p>
-<table>
+<table class="table">
 <thead>
 <tr>
 <th>Property</th>
@@ -153,7 +175,7 @@
 </tbody>
 </table>
 <p>Once started, the values of these properties are printed to the console.</p>
-<h2 id="configurations">Configurations</h2>
+<h2 id="configurations">Configurations<a class="headerlink" href="#configurations" title="Permanent link">&para;</a></h2>
 <p>Configuration files are plain property files (<code>java.util.Property</code>). The format is simple:</p>
 <div class="codehilite"><pre><span class="n">file</span> <span class="p">::=</span> <span class="p">(</span> <span class="n">header</span> <span class="o">|</span> <span class="n">comment</span> <span class="p">)</span> <span class="o">*</span>
 <span class="n">header</span> <span class="p">::=</span> <span class="o">&lt;</span><span class="n">header</span><span class="o">&gt;</span> <span class="p">(</span> <span class="s">&#39;:&#39;</span> <span class="o">|</span> <span class="s">&#39;=&#39;</span> <span class="p">)</span> <span class="o">&lt;</span><span class="n">value</span><span class="o">&gt;</span> <span class="p">(</span> <span class="s">&#39;\&lt;nl&gt; &lt;value&gt; ) *</span>
@@ -182,14 +204,14 @@
 
 
 <p>If a configuration managed by File Install is modified, File Install will write the configuration back to a property file to ensure peristence across restarts.</p>
-<h2 id="property-substitution-in-configuration-files">Property substitution in configuration files</h2>
+<h2 id="property-substitution-in-configuration-files">Property substitution in configuration files<a class="headerlink" href="#property-substitution-in-configuration-files" title="Permanent link">&para;</a></h2>
 <p>It is possible to use system properties to specify the values of properties in configuration files. This is achieved through system property substitution, which is instigated by using <code>$\{&lt;property&gt;\</code>} syntax, where <property> is the name of a system property to substitute.  Bundle context properties will take precedence over system properties if available.
 Example:</p>
 <div class="codehilite"><pre>ftp.port = <span class="cp">${</span><span class="n">system</span><span class="o">.</span><span class="n">ftp</span><span class="o">.</span><span class="n">port</span><span class="cp">}</span>
 </pre></div>
 
 
-<h2 id="watching-multiple-directories-with-file-install">Watching multiple directories with File Install</h2>
+<h2 id="watching-multiple-directories-with-file-install">Watching multiple directories with File Install<a class="headerlink" href="#watching-multiple-directories-with-file-install" title="Permanent link">&para;</a></h2>
 <p>Starting with version 3.1.0 it is possible to specify several directories to watch with the system property <code>felix.fileinstall.dir</code>; this property can either point to a single directory or a comma separated list of directories. In addition, Apache Felix File Install provides a ManagedServiceFactory to create multiple instances of File Install. Asuming you have a File Install bundle watching a <code>bundles</code> folder, creating a new instance is as simple as creating a new configuration file <code>org.apache.felix.fileinstall-&lt;pid&gt;.cfg</code> in that folder (substitute <pid> with a unique Id for the new service instance):</p>
 <DIV class="code panel" style="border-style: solid;border-width: 1px;"><DIV class="codeHeader panelHeader" style="border-bottom-width: 1px;border-bottom-style: solid;"><B>org.apache.felix.fileinstall-configDir.cfg</B></DIV><DIV class="codeContent panelContent">
     felix.fileinstall.poll=2000
@@ -208,7 +230,7 @@ Apache Felix File Install can support de
 
 To add support for a custom artifact, a service implementing one of `org.apache.felix.fileinstall.ArtifactListener`'s sub interfaces must be registered in the OSGi registry.
       <div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
-        Rev. 1422427 by fmeschbe on Sun, 16 Dec 2012 00:36:51 +0000
+        Rev. 1700393 by cziegeler on Tue, 1 Sep 2015 06:04:06 +0000
       </div>
       <div class="trademarkFooter"> 
         Apache Felix, Felix, Apache, the Apache feather logo, and the Apache Felix project

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework-security.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework-security.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework-security.html Tue Sep  1 06:05:17 2015
@@ -39,7 +39,18 @@
     </div>
     
     <div class="menu"> 
-      <p><a href="/news.html">news</a>  <br />
+      <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 />
@@ -66,11 +77,22 @@
       </div>
 
       <h1>Apache Felix Framework Security</h1>
-      <p>The Felix Framework Security subproject is an implementation of the security part of the OSGi R4.2 core specification.</p>
-<h1 id="installing">Installing</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>
+<p>The Felix Framework Security subproject is an implementation of the security part of the OSGi R4.2 core specification.</p>
+<h1 id="installing">Installing<a class="headerlink" href="#installing" title="Permanent link">&para;</a></h1>
 <p>Support for the OSGi r4.2 security specifications including PermissionAdmin and ConditionalPermissionAdmin is provided by the framework.security extension bundle. The bundle provides both, the packages as well as the services when it is installed. </p>
 <p>All that needs to be done is to install the org.apache.felix.framework.security bundle into the framework. </p>
-<h1 id="using-security">Using security</h1>
+<h1 id="using-security">Using security<a class="headerlink" href="#using-security" title="Permanent link">&para;</a></h1>
 <p>Besides installing the security bundle three properties should be specified:
 <em> org.osgi.framework.security="osgi"
 </em> java.security.policy=all.policy
@@ -106,7 +128,7 @@ The third, allows to specify a File.path
     objectClass = org.osgi.service.condpermadmin.ConditionalPermissionAdmin
     service.id = 4
       <div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
-        Rev. 1422427 by fmeschbe on Sun, 16 Dec 2012 00:36:51 +0000
+        Rev. 1700393 by cziegeler on Tue, 1 Sep 2015 06:04:06 +0000
       </div>
       <div class="trademarkFooter"> 
         Apache Felix, Felix, Apache, the Apache feather logo, and the Apache Felix project

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework.html Tue Sep  1 06:05:17 2015
@@ -39,7 +39,18 @@
     </div>
     
     <div class="menu"> 
-      <p><a href="/news.html">news</a>  <br />
+      <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 />
@@ -66,9 +77,20 @@
       </div>
 
       <h1>Apache Felix Framework</h1>
-      <h1 id="apache-felix-framework">Apache Felix Framework</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="apache-felix-framework">Apache Felix Framework<a class="headerlink" href="#apache-felix-framework" title="Permanent link">&para;</a></h1>
 <p>The Felix Framework subproject is an implementation of the OSGi R5 core framework specification.</p>
-<h2 id="framework-documentation">Framework documentation</h2>
+<h2 id="framework-documentation">Framework documentation<a class="headerlink" href="#framework-documentation" title="Permanent link">&para;</a></h2>
 <ul>
 <li><a href="/documentation/subprojects/apache-felix-framework/apache-felix-framework-and-alternative-java-vms.html">Apache Felix Framework and Alternative Java VMs</a></li>
 <li><a href="/documentation/subprojects/apache-felix-framework/apache-felix-framework-and-google-android.html">Apache Felix Framework and Google Android</a></li>
@@ -81,7 +103,7 @@
 <li><a href="/documentation/subprojects/apache-felix-framework/apache-felix-framework-usage-documentation.html">Apache Felix Framework Usage Documentation</a></li>
 </ul>
       <div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
-        Rev. 1591313 by cziegeler on Wed, 30 Apr 2014 14:27:38 +0000
+        Rev. 1700393 by cziegeler on Tue, 1 Sep 2015 06:04:06 +0000
       </div>
       <div class="trademarkFooter"> 
         Apache Felix, Felix, Apache, the Apache feather logo, and the Apache Felix project

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-and-alternative-java-vms.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-and-alternative-java-vms.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-and-alternative-java-vms.html Tue Sep  1 06:05:17 2015
@@ -39,7 +39,18 @@
     </div>
     
     <div class="menu"> 
-      <p><a href="/news.html">news</a>  <br />
+      <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 />
@@ -68,7 +79,7 @@
       <h1>Apache Felix Framework and Alternative Java VMs</h1>
       
       <div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
-        Rev. 1422427 by fmeschbe on Sun, 16 Dec 2012 00:36:51 +0000
+        Rev. 1700393 by cziegeler on Tue, 1 Sep 2015 06:04:06 +0000
       </div>
       <div class="trademarkFooter"> 
         Apache Felix, Felix, Apache, the Apache feather logo, and the Apache Felix project

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-and-google-android.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-and-google-android.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-and-google-android.html Tue Sep  1 06:05:17 2015
@@ -39,7 +39,18 @@
     </div>
     
     <div class="menu"> 
-      <p><a href="/news.html">news</a>  <br />
+      <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 />
@@ -66,11 +77,22 @@
       </div>
 
       <h1>Apache Felix Framework and Google Android</h1>
-      <h1 id="apache-felix-framework-and-google-android">Apache Felix Framework and Google Android</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="apache-felix-framework-and-google-android">Apache Felix Framework and Google Android<a class="headerlink" href="#apache-felix-framework-and-google-android" title="Permanent link">&para;</a></h1>
 <p>The purpose of this document is to explain how to use <a href="http://felix.apache.org">Apache Felix</a> on Google's new mobile phone platform - [Android|http://code.google.com/android].</p>
-<h2 id="dalvik-vm">Dalvik VM</h2>
+<h2 id="dalvik-vm">Dalvik VM<a class="headerlink" href="#dalvik-vm" title="Permanent link">&para;</a></h2>
 <p>Google Android SDK allows developers to write Java code in order to create Android applications. Instead of a regular Java Virtual Machine that executes this code, a special-purpose virtual machine named Dalvik is being used in order to comply with mobile platform requirements. Dalvik does not use Java bytecode format, but, a tool named dx, included in the Android SDK, transforms the Java class files of Java classes compiled by a regular Java compiler into another class file format (the .dex format) (the conversion is not done at runtime).</p>
-<h2 id="preparing-bundles">Preparing bundles</h2>
+<h2 id="preparing-bundles">Preparing bundles<a class="headerlink" href="#preparing-bundles" title="Permanent link">&para;</a></h2>
 <p>Although Felix, since version 1.0.3, has built in support for Android, there are still some things needed to be done in order to successfully make use of it ( you will need to install <a href="http://code.google.com/android/download.html">Android SDK</a> and you should have <android*SDK*HOME>/tools added to system PATH variable). The zip file available for download has been created in the same manner.</p>
 <p><em>Step 1</em>: Each JAR file you use, either as a Felix library or as a bundle, should contain its DEX equivalent. This means that you must first create a DEX file for your JAR:</p>
 <div class="codehilite"><pre><span class="n">dx</span> <span class="o">--</span><span class="n">dex</span> <span class="o">--</span><span class="n">output</span><span class="p">=</span><span class="n">classes</span><span class="p">.</span><span class="n">dex</span> <span class="n">JAR_file</span><span class="p">.</span><span class="n">jar</span>
@@ -127,7 +149,7 @@
 </pre></div>
 
 
-<h2 id="launching-felix">Launching Felix</h2>
+<h2 id="launching-felix">Launching Felix<a class="headerlink" href="#launching-felix" title="Permanent link">&para;</a></h2>
 <p>Once you've done that, you should be able to launch Felix and the bundles on Android: start emulator shell, change directory to the location of your Felix files and execute felix.sh.</p>
 <div class="codehilite"><pre><span class="n">adb</span> <span class="n">shell</span>
 <span class="n">cd</span> <span class="o">/</span><span class="n">data</span><span class="o">/</span><span class="n">felix</span>
@@ -154,12 +176,12 @@
 </pre></div>
 
 
-<h2 id="embedding-felix">Embedding Felix</h2>
+<h2 id="embedding-felix">Embedding Felix<a class="headerlink" href="#embedding-felix" title="Permanent link">&para;</a></h2>
 <p>Apache Felix can also be integrated with an Android application. To achieve this, you need to embed Felix into <code>onCreate()</code> method of your Activity class (see Android docs for more details on how to use an Activity) and process your bundles as shown above.</p>
-<h2 id="download">Download</h2>
+<h2 id="download">Download<a class="headerlink" href="#download" title="Permanent link">&para;</a></h2>
 <p>The project zip file <a href="">osgi-android.zip</a></p>
       <div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
-        Rev. 1422427 by fmeschbe on Sun, 16 Dec 2012 00:36:51 +0000
+        Rev. 1700393 by cziegeler on Tue, 1 Sep 2015 06:04:06 +0000
       </div>
       <div class="trademarkFooter"> 
         Apache Felix, Felix, Apache, the Apache feather logo, and the Apache Felix project

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-bundle-cache.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-bundle-cache.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-bundle-cache.html Tue Sep  1 06:05:17 2015
@@ -39,7 +39,18 @@
     </div>
     
     <div class="menu"> 
-      <p><a href="/news.html">news</a>  <br />
+      <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 />
@@ -66,15 +77,26 @@
       </div>
 
       <h1>Apache Felix Framework Bundle Cache</h1>
-      <h1 id="apache-felix-framework-bundle-cache">Apache Felix Framework Bundle Cache</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="apache-felix-framework-bundle-cache">Apache Felix Framework Bundle Cache<a class="headerlink" href="#apache-felix-framework-bundle-cache" title="Permanent link">&para;</a></h1>
 <ul>
 <li><a href="">Introduction</a></li>
 <li><a href="">Default Behavior</a></li>
 <li><a href="">Configuring Default Behavior</a></li>
 </ul>
-<h1 id="introduction">Introduction</h1>
+<h1 id="introduction">Introduction<a class="headerlink" href="#introduction" title="Permanent link">&para;</a></h1>
 <p>The OSGi specification states that the framework must cache bundles and their run-time state, but it does not explicitly define how this should be done. As a result, each OSGi framework implementation is likely to cache bundles differently. This document describes in detail how the Felix framework handles bundle caching by default and also describes the mechanisms to modify this default behavior.</p>
-<h1 id="default-behavior">Default Behavior</h1>
+<h1 id="default-behavior">Default Behavior<a class="headerlink" href="#default-behavior" title="Permanent link">&para;</a></h1>
 <p>Since the OSGi R4.2 specification, the standard framework launching and embedding API requires that frameworks should use "reasonable defaults" for all configuration properties so it is possible to start a framework without any configuration. One such default value is the location of the framework bundle cache. When the Felix framework is start, it creates a bundle cache directory, called <code>felix-cache</code>, in the current working directory by default. All bundle information is saved inside the bundle cache directory.</p>
 <p>The structure of a bundle cache directory is reasonably simple; it contains a directory for each bundle, where the directory name corresponds to the bundle identifier number. Each bundle directory contains a file for the bundle's location, identifier, start level, state, and a directory containing the bundle JAR file and any extracted embedded JAR files or native libraries if any exist. As an example, the bundle cache directory for a bundle containing an embedded JAR file and a native library looks like this:</p>
 <div class="codehilite"><pre>   <span class="cp">${</span><span class="n">user</span><span class="o">.</span><span class="n">dir</span><span class="cp">}</span>
@@ -104,7 +126,7 @@
 <p>To illustrate, upon initial installation, the bundle JAR file is placed into a revision directory named <code>revision0.0</code>. When an update is performed, the updated bundle JAR file is placed in a directory named <code>revision0.1</code>. If another update is performed without a refresh of the framework, the newer revision will be placed into a directory named <code>revision0.2</code> and so on. When the framework is refreshed or shutdown, all revision directories are purged from the bundle cache and only the most recent revision directory is maintained.</p>
 <p>Simply purging the old revision directories may appear adequate for refreshing the framework, but it is not due to how the JVM handles native libraries. When a native library is loaded it is associated with a specific class loader; no other class loader can load the same native library. The uniqueness of a native library is determined by its absolute path in the file system. Consequently, when the framework is refreshed, it is necessary to recreate the class loaders for all refreshed bundles. If a refreshed bundle has a native library, then this would result in an exception since the native library is still associated with the prior class loader; the refresh counter remedies this situation.</p>
 <p>After purging all old revision directories, the current revision directory is renamed based on the current refresh count. By renaming the directory, it is possible to re-load the native library since its path in the file system has changed. The old class loaders and native libraries will eventually be garbage collected. The current refresh count is stored in a file, called <code>refresh.counter</code>, in the bundle's directory. To illustrate, if a bundle was updated and has two revision directories, <code>revision0.0</code> and <code>revision0.1</code>, after a refresh the older revision directory will be deleted and the newest revision directory will be renamed to <code>revision1.0</code>. If the bundle is refresh again, its revision directory will become <code>revision2.0</code> and so on. Note: Bundles may be refreshed when they are updated or when they depend on other bundles that have been updated; either way it is necessary to increment the refresh count and rename the rev
 ision directory during a refresh operation.</p>
-<h1 id="configuring-default-behavior">Configuring Default Behavior</h1>
+<h1 id="configuring-default-behavior">Configuring Default Behavior<a class="headerlink" href="#configuring-default-behavior" title="Permanent link">&para;</a></h1>
 <p>It is possible to modify the default behavior of Felix' bundle cache by setting certain configuration properties; see the <a href="">usage document</a> for information on how to set configuration properties for Felix. Felix' bundle cache recognizes the following configuration properties:</p>
 <ul>
 <li><code>org.osgi.framework.storage</code> - Sets the directory to use as the bundle cache; by default bundle cache directory is <code>felix-cache</code> in the current working directory. The value should be a valid directory name. The directory name can be either absolute or relative. Relative directory names are relative to the current working directory. The specified directory will be created if it does not exist.</li>
@@ -114,7 +136,7 @@
 </ul>
 <p>To be clear, if a relative bundle cache directory is specified then the absolute location of the bundle cache directory is computed like this: <code>$\{felix.cache.rootdir}+$\{org.osgi.framework.storage</code>}, where <code>felix.cache.rootdir</code> has the default value of the current working directory. If <code>$\{org.osgi.framework.storage</code>} is specified as absolute, then it is used as the location of the bundle cache. If the bundle cache directory does not exist, it is created.</p>
       <div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
-        Rev. 1422427 by fmeschbe on Sun, 16 Dec 2012 00:36:51 +0000
+        Rev. 1700393 by cziegeler on Tue, 1 Sep 2015 06:04:06 +0000
       </div>
       <div class="trademarkFooter"> 
         Apache Felix, Felix, Apache, the Apache feather logo, and the Apache Felix project

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-configuration-properties.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-configuration-properties.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-configuration-properties.html Tue Sep  1 06:05:17 2015
@@ -39,7 +39,18 @@
     </div>
     
     <div class="menu"> 
-      <p><a href="/news.html">news</a>  <br />
+      <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 />
@@ -66,7 +77,18 @@
       </div>
 
       <h1>Apache Felix Framework Configuration Properties</h1>
-      <h1 id="apache-felix-framework-configuration-properties">Apache Felix Framework Configuration Properties</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="apache-felix-framework-configuration-properties">Apache Felix Framework Configuration Properties<a class="headerlink" href="#apache-felix-framework-configuration-properties" title="Permanent link">&para;</a></h1>
 <ul>
 <li><a href="">Overview</a></li>
 <li><a href="">Framework configuration properties</a></li>
@@ -74,10 +96,10 @@
 <li><a href="">Mirgrating from earlier versions</a></li>
 <li><a href="">Feedback</a></li>
 </ul>
-<h2 id="overview">Overview</h2>
+<h2 id="overview">Overview<a class="headerlink" href="#overview" title="Permanent link">&para;</a></h2>
 <p>This document describes the various configuration properties related to the Apache Felix Framework. Technically, there are framework properties and launcher properties. If you are using the Felix Framework JAR file (i.e., <code>org.apache.felix.framework-x.y.x.jar</code>), then you can only use framework properties. On the other hand, if you are using the Felix Main launcher JAR (i.e., <code>felix.jar</code> or <code>org.apache.felix.main-x.y.z.jar</code>), then you can use both framework and launcher properties. This document will describe both sets of properties.</p>
 <p>Note that the framework does not use system properties to find its configuration properties, it only consults the map passed into its constructor. In contrast to bundles, which use <code>BundleContext.getProperty()</code>, which exposes both configuration and system properties at execution time. In the case of overlap, the configuration properties override system properties. As a convenience, if you are using the Felix launcher, it will copy all configuration properties it finds in the system properties to the configuration map passed into the framework constructor, which allows you to set configuration properties on the command line. This feature is <em>not</em> available if you are just using the Felix framework JAR file.</p>
-<h2 id="framework-configuration-properties">Framework configuration properties</h2>
+<h2 id="framework-configuration-properties">Framework configuration properties<a class="headerlink" href="#framework-configuration-properties" title="Permanent link">&para;</a></h2>
 <p>The following configuration properties are for the framework (properties starting with "<code>felix</code>" are specific to Felix, while those starting with "<code>org.osgi</code>" are standard OSGi properties):</p>
 <ul>
 <li><code>org.osgi.framework.executionenvironment</code> - Sets the OSGi execution environment for the framework. The framework tries to set this to a reasonable default value. If you specify a value, it overrides the framework default. Refer to the OSGi specification for appropriate execution environment values.</li>
@@ -101,7 +123,7 @@
 <li><code>felix.native.processor.alias.&lt;procName&gt;</code> - An alias for resolving native processor requirements new with R6.  This can be used to add new or override existing processors.  The <procName> represents the key for the processor architecture such as x86-64 (which may not contain spaces) then the property value is a comma delimited list of aliases such as x86_64,amd64.  EX felix.native.processor.alias.x86-64=x86_64,amd64</li>
 <li><code>felix.native.osname.alias.&lt;osName&gt;</code> - An alias for resolving native operating system requirements new with R6.  This can be used to add new or override existing operating systems.  The <osName> represents the key for the operating system such as windows7 (which may not contain spaces) then the property value is a comma delimited list of aliases such as Windows 7,win32.  EX felix.native.osname.alias.windows7=Windows 7,win32</li>
 </ul>
-<h2 id="launcher-configuration-properties">Launcher configuration properties</h2>
+<h2 id="launcher-configuration-properties">Launcher configuration properties<a class="headerlink" href="#launcher-configuration-properties" title="Permanent link">&para;</a></h2>
 <p>The following configuration properties are for the launcher:</p>
 <ul>
 <li><code>felix.auto.deploy.dir</code> - Specifies the auto-deploy directory from which bundles are automatically deployed at framework startup. The default is the <code>bundle/</code> directory of the current directory.</li>
@@ -110,7 +132,7 @@
 <li><code>felix.auto.start.&lt;n&gt;</code> - Space-delimited list of bundle URLs to automatically install and start when Felix is started, where <code>&lt;n&gt;</code> is the start level into which the bundle will be installed (e.g., <code>felix.auto.start.2</code>).</li>
 <li><code>felix.shutdown.hook</code> - Specifies whether the launcher should install a shutdown hook to cleanly shutdown the framework on process exit. The default value is <code>true</code>.</li>
 </ul>
-<h2 id="migrating-from-earlier-versions">Migrating from Earlier Versions</h2>
+<h2 id="migrating-from-earlier-versions">Migrating from Earlier Versions<a class="headerlink" href="#migrating-from-earlier-versions" title="Permanent link">&para;</a></h2>
 <p>Apache Felix Framework <code>2.0.0</code> introduced significant configuration property changes. This section describes the differences from older versions of the framework.</p>
 <ul>
 <li><em>Removed</em>
@@ -128,10 +150,10 @@
 ** <code>felix.cache.rootdir</code> - Introduced as a result of removing bundle profiles to help resolve relative bundle cache directories.</li>
 </ul>
 <p>For the most part, these changes are minor and previous behavior achieved from older configuration properties is either easily attained with the new properties or no longer necessary.</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="">users-subscribe@felix.apache.org</a>; after subscribing, email questions or feedback to [users@felix.apache.org|mailto:users@felix.apache.org].</p>
       <div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
-        Rev. 1653725 by bob on Thu, 22 Jan 2015 00:56:25 +0000
+        Rev. 1700393 by cziegeler on Tue, 1 Sep 2015 06:04:06 +0000
       </div>
       <div class="trademarkFooter"> 
         Apache Felix, Felix, Apache, the Apache feather logo, and the Apache Felix project

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-faq.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-faq.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-faq.html Tue Sep  1 06:05:17 2015
@@ -39,7 +39,18 @@
     </div>
     
     <div class="menu"> 
-      <p><a href="/news.html">news</a>  <br />
+      <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 />
@@ -66,7 +77,18 @@
       </div>
 
       <h1>Apache Felix Framework FAQ</h1>
-      <h1 id="apache-felix-framework-frequently-asked-questions">Apache Felix Framework Frequently Asked Questions</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="apache-felix-framework-frequently-asked-questions">Apache Felix Framework Frequently Asked Questions<a class="headerlink" href="#apache-felix-framework-frequently-asked-questions" title="Permanent link">&para;</a></h1>
 <div class="toc">
 <ul>
 <li><a href="#apache-felix-framework-frequently-asked-questions">Apache Felix Framework Frequently Asked Questions</a><ul>
@@ -79,13 +101,13 @@
 </li>
 </ul>
 </div>
-<h2 id="is-the-felix-framework-compliant-with-the-osgi-specification">Is the Felix framework compliant with the OSGi specification?</h2>
+<h2 id="is-the-felix-framework-compliant-with-the-osgi-specification">Is the Felix framework compliant with the OSGi specification?<a class="headerlink" href="#is-the-felix-framework-compliant-with-the-osgi-specification" title="Permanent link">&para;</a></h2>
 <p>Refer to the <a href="/documentation/subprojects/apache-felix-framework/apache-felix-framework-osgi-r4-2-ct-results.html">Apache Felix Framework OSGi R4.2 CT Results</a> document.</p>
-<h2 id="if-i-use-bundles-from-felix-will-my-application-be-tied-to-the-felix-framework">If I use bundles from Felix, will my application be tied to the Felix framework?</h2>
+<h2 id="if-i-use-bundles-from-felix-will-my-application-be-tied-to-the-felix-framework">If I use bundles from Felix, will my application be tied to the Felix framework?<a class="headerlink" href="#if-i-use-bundles-from-felix-will-my-application-be-tied-to-the-felix-framework" title="Permanent link">&para;</a></h2>
 <p>See the answer in the <a href="">OSGi FAQ</a>.</p>
-<h2 id="when-i-update-my-bundle-why-are-my-bundles-old-classes-still-being-used">When I update my bundle, why are my bundle's old classes still being used?</h2>
+<h2 id="when-i-update-my-bundle-why-are-my-bundles-old-classes-still-being-used">When I update my bundle, why are my bundle's old classes still being used?<a class="headerlink" href="#when-i-update-my-bundle-why-are-my-bundles-old-classes-still-being-used" title="Permanent link">&para;</a></h2>
 <p>See the answer in the <a href="">OSGi FAQ</a>.</p>
-<h2 id="why-do-i-get-an-unknown-protocol-http-exception-when-i-run-felix-on-a-non-sun-jre">Why do I get an "Unknown protocol: http" exception when I run Felix on a non-Sun JRE?</h2>
+<h2 id="why-do-i-get-an-unknown-protocol-http-exception-when-i-run-felix-on-a-non-sun-jre">Why do I get an "Unknown protocol: http" exception when I run Felix on a non-Sun JRE?<a class="headerlink" href="#why-do-i-get-an-unknown-protocol-http-exception-when-i-run-felix-on-a-non-sun-jre" title="Permanent link">&para;</a></h2>
 <p>Felix installs the URL Handlers service by default. If you do not want this service you can disable it, by setting the <code>felix.service.urlhandlers</code> property to <code>false</code> in the <code>config.properties</code> file. It is not recommended to disable this, but the main reason for doing so it because the URL Handlers implementation invokes methods to set the singleton factories for URL stream and content handler factories. Assuming that you want to use URL Handlers service, you must configure it if you aren't running on the standard Sun JRE.</p>
 <p>The URL Handlers service extends the standard Java URL stream and content handler mechanism to work in an OSGi environment. The way that built-in URL protocol and content handlers are discovered is by probing packages for the appropriate classes to handle the protocol/content. For example, the default package for Sun protocol handlers is:</p>
 <div class="codehilite"><pre><span class="n">sun</span><span class="p">.</span><span class="n">net</span><span class="p">.</span><span class="n">www</span><span class="p">.</span><span class="n">protocol</span>
@@ -114,11 +136,11 @@
 
 <p>The value of these properties is a list of "|" delimited package names to be searched for protocol and content handlers, respectively. See the Java documentation for <a href="http://java.sun.com/javase/6/docs/api/java/net/URL.html#URL(java.lang.String,%20java.lang.String,%20int,%20java.lang.String)">stream</a> and [content|http://java.sun.com/javase/6/docs/api/java/net/URLConnection.html#getContent()] handlers for more information.</p>
 <p>There are two ways to set these system properties. The first way is using the standard <code>-D&lt;property&gt;=&lt;value&gt;</code> syntax when executing <code>java</code> or if you are using Felix' standard <code>Main.java</code> launcher, you can put the system properties into the <code>conf/system.properties</code> file so that they get set automatically each time you execute Felix.</p>
-<h2 id="what-is-the-daemon-status-of-framework-created-threads">What is the daemon status of framework created threads?</h2>
+<h2 id="what-is-the-daemon-status-of-framework-created-threads">What is the daemon status of framework created threads?<a class="headerlink" href="#what-is-the-daemon-status-of-framework-created-threads" title="Permanent link">&para;</a></h2>
 <p>The framework creates a few threads for handling specific tasks, such as event delivery or handling start level change requests. All framework threads are explicitly started as daemon threads except the event dispatcher thread. The logic behind this is that the event dispatcher thread should exit when it is done delivering events. However, if an application is hosting an instance of the framework, it is possible to make the event dispatcher thread a daemon by starting your framework instance from a daemon thread, in which case the event dispatcher thread will inherit this setting.</p>
 <p>For bundle developers, it is probably best to explicitly define any created threads as daemon or non-daemon to avoid any ambiguity.</p>
       <div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
-        Rev. 1422427 by fmeschbe on Sun, 16 Dec 2012 00:36:51 +0000
+        Rev. 1700393 by cziegeler on Tue, 1 Sep 2015 06:04:06 +0000
       </div>
       <div class="trademarkFooter"> 
         Apache Felix, Felix, Apache, the Apache feather logo, and the Apache Felix project

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-launching-and-embedding.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-launching-and-embedding.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-launching-and-embedding.html Tue Sep  1 06:05:17 2015
@@ -39,7 +39,18 @@
     </div>
     
     <div class="menu"> 
-      <p><a href="/news.html">news</a>  <br />
+      <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 />
@@ -66,7 +77,18 @@
       </div>
 
       <h1>Apache Felix Framework Launching and Embedding</h1>
-      <h1 id="apache-felix-framework-launching-and-embedding">Apache Felix Framework Launching and Embedding</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="apache-felix-framework-launching-and-embedding">Apache Felix Framework Launching and Embedding<a class="headerlink" href="#apache-felix-framework-launching-and-embedding" title="Permanent link">&para;</a></h1>
 <p><em>[This document describes framework launching introduced in Felix Framework 2.0.0 and continuing with the latest releases; it is incompatible with older versions of the Felix framework.]()</em></p>
 <ul>
 <li><a href="">Introduction</a></li>
@@ -86,9 +108,9 @@
 <li><a href="">Caveat</a></li>
 <li><a href="">Feedback</a></li>
 </ul>
-<h1 id="introduction">Introduction</h1>
+<h1 id="introduction">Introduction<a class="headerlink" href="#introduction" title="Permanent link">&para;</a></h1>
 <p>The Apache Felix Framework is intended to be easily launchable and embeddable. For example, the Felix framework implementation avoids the use of system properties for configuration, since these are globals and can cause interference if multiple framework instances are created in the same VM. The framework also tries to multiplex singleton facilities, like the URL stream handler factory. The goal is to make it possible to use the framework in a variety of scenarios; however, this is still just a goal. In other words, this is a work in progress and if any issues arise, it would be greatly appreciated if they are brought to the attention of the Felix community. The next section provides an overview of the standard OSGi launching and embedding API for frameworks, while the remainder of the document is divided into two sections, one focusing on how to launch Felix and one focusing on how to embed Felix into a host application.</p>
-<h1 id="osgi-launching-and-embedding-api-overview">OSGi Launching and Embedding API Overview</h1>
+<h1 id="osgi-launching-and-embedding-api-overview">OSGi Launching and Embedding API Overview<a class="headerlink" href="#osgi-launching-and-embedding-api-overview" title="Permanent link">&para;</a></h1>
 <p>The Felix framework is implemented by the <code>org.apache.felix.framework.Felix</code> class or just <code>Felix</code> for short. As part of the R4.2 OSGi specification, the launching and embedding API of the OSGi framework has been standardized. The approach is to have the framework implement the <code>org.osgi.framework.launch.Framework</code> interface, which extends the <code>org.osgi.framework.Bundle</code> interface. These interfaces provide the necessary means to launch and manage framework instances. The <code>Bundle</code> interface is defined as:</p>
 <div class="codehilite"><pre><span class="n">public</span> <span class="n">interface</span> <span class="n">Bundle</span>
 <span class="p">{</span>
@@ -137,14 +159,14 @@
 
 
 <p>The framework factory can be used to create configured framework instances. It is obtained following the standard <code>META-INF/services</code> approach.</p>
-<h2 id="creating-and-configuring-the-framework-instance">Creating and Configuring the Framework Instance</h2>
+<h2 id="creating-and-configuring-the-framework-instance">Creating and Configuring the Framework Instance<a class="headerlink" href="#creating-and-configuring-the-framework-instance" title="Permanent link">&para;</a></h2>
 <p>You use the framework factory to construct and configure a framework instance (or by directly instantiating the Felix class). The configuration map may contain any of the framework configuration properties listed in the <a href="/documentation/subprojects/apache-felix-framework/apache-felix-framework-configuration-properties.html">Apache Felix Framework Configuration Properties</a> document, not the launcher configuration properties. The configuration map is copied and the keys are treated as case insensitive. You are not able to change the framework's configuration after construction. If you need a different configuration, you must create a new framework instance.</p>
 <div class="warning" markdown="1">
 **WARNING**
 Felix configuration properties have change considerably starting from `1.4.0`; if you are upgrading from an earlier version, the [configuration property document]() describes the configuration property changes.
 </div>
 
-<h2 id="starting-the-framework-instance">Starting the Framework Instance</h2>
+<h2 id="starting-the-framework-instance">Starting the Framework Instance<a class="headerlink" href="#starting-the-framework-instance" title="Permanent link">&para;</a></h2>
 <p>The <code>start()</code> method is used to start the framework instance. If the <code>init()</code> method was not invoked prior to calling <code>start()</code>, then it is invoked by <code>start()</code>. The two methods result in two different framework state transitions:</p>
 <ul>
 <li><code>init()</code> results in the framework instance in the <code>Bundle.STARTING</code> state.</li>
@@ -161,9 +183,9 @@ Felix configuration properties have chan
 <li>The framework enters the <code>Bundle.STARTING</code> state.</li>
 </ul>
 <p>A call to <code>start()</code> is necessary to start the framework instance, if the <code>init()</code> method is invoked manually. Invoking <code>init()</code> or <code>start()</code> on an already started framework as no effect.</p>
-<h2 id="stopping-the-framework-instance">Stopping the Framework Instance</h2>
+<h2 id="stopping-the-framework-instance">Stopping the Framework Instance<a class="headerlink" href="#stopping-the-framework-instance" title="Permanent link">&para;</a></h2>
 <p>To stop the framework instance, invoke the <code>stop()</code> method, which will asynchronously stop the framework. To know when the framework has finished its shutdown sequence, use the <code>waitForStop()</code> method to wait until it is complete. A stopped framework will be in the <code>Bundle.RESOLVED</code> state. It is possible to restart the framework, using the normal combination of <code>init()</code>/<code>start()</code> methods as previously described.</p>
-<h1 id="launching-a-framework">Launching a Framework</h1>
+<h1 id="launching-a-framework">Launching a Framework<a class="headerlink" href="#launching-a-framework" title="Permanent link">&para;</a></h1>
 <p>Launching a framework is fairly simple and involves only four steps:</p>
 <ol>
 <li>Define some configuration properties.</li>
@@ -173,7 +195,7 @@ Felix configuration properties have chan
 </ol>
 <p>In reality, the first step is optional, since all properties will have reasonable defaults, but if you are creating a launcher you will generally want to more than that, such as automatically installing and starting bundles when you start the framework instance. The default Felix launcher defines reusable functionality to automatically install and/or start bundles upon framework startup; see the <a href="">usage document</a> for more information on configuring the Felix framework and on the various configuration properties.</p>
 <p>The remainder of this section describes how the standard Felix launcher works as well as how to create a custom launcher.</p>
-<h2 id="standard-felix-framework-launcher">Standard Felix Framework Launcher</h2>
+<h2 id="standard-felix-framework-launcher">Standard Felix Framework Launcher<a class="headerlink" href="#standard-felix-framework-launcher" title="Permanent link">&para;</a></h2>
 <p>The standard Felix framework launcher is very simple and is not intended to solve every possible requirement; it is intended to work for most standard situations. Most special launching requirements should be resolved by creating a custom launcher. This section describes how the standard launcher works. The following code represents the complete <code>main()</code> method of the standard launcher, each numbered comment will be described in more detail below:</p>
 <div class="codehilite"><pre><span class="n">public</span> <span class="n">static</span> <span class="n">void</span> <span class="n">main</span><span class="p">(</span><span class="n">String</span><span class="p">[]</span> <span class="n">args</span><span class="p">)</span> <span class="n">throws</span> <span class="n">Exception</span>
 <span class="p">{</span>
@@ -292,7 +314,7 @@ Felix configuration properties have chan
 <li>Invoke <code>waitForStop()</code> to wait for the framework to stop to force the VM to exit; this is necessary because the framework never calls <code>System.exit()</code> and some libraries (e.g., Swing) create threads that will not allow the VM to exit.</li>
 </ol>
 <p>The framework is not active until the <code>start()</code> method is called. If no shell bundles are installed and started or if there is difficulty locating the shell bundles specified in the auto-start property, then it will appear as if the framework is hung, but it is actually running without any way to interact with it since the shell bundles provide the only means of interaction.</p>
-<h2 id="custom-framework-launcher">Custom Framework Launcher</h2>
+<h2 id="custom-framework-launcher">Custom Framework Launcher<a class="headerlink" href="#custom-framework-launcher" title="Permanent link">&para;</a></h2>
 <p>This section creates a bare-bones launcher to demonstrate the minimum requirements for creating an interactive launcher for the Felix framework. This example uses the standard Gogo shell bundles for interactivity, but any other bundles could be used instead. This example launcher project has the following directory structure:</p>
 <div class="codehilite"><pre><span class="n">launcher</span><span class="o">/</span>
    <span class="n">lib</span><span class="o">/</span>
@@ -411,9 +433,9 @@ Felix configuration properties have chan
 
 
 <p>After executing this command, a "<code>felix-cache/</code>" directory is created that contains the cached bundles, which were installed from the <code>bundle/</code> directory.</p>
-<h1 id="embedding-the-felix-framework">Embedding the Felix Framework</h1>
+<h1 id="embedding-the-felix-framework">Embedding the Felix Framework<a class="headerlink" href="#embedding-the-felix-framework" title="Permanent link">&para;</a></h1>
 <p>Embedding the Felix framework into a host application is a simple way to provide a sophisticated extensibility mechanism (i.e., a plugin system) to the host application. Embedding the Felix framework is very similar to launching it as described above, the main difference is that the host application typically wants to interact with the framework instance and/or installed bundles/services from the outside. This is fairly easy to achieve, but there are some subtle issues to understand. This section presents the mechanisms for embedding Felix into a host application and the issues in doing so.</p>
-<h2 id="hostfelix-interaction">Host/Felix Interaction</h2>
+<h2 id="hostfelix-interaction">Host/Felix Interaction<a class="headerlink" href="#hostfelix-interaction" title="Permanent link">&para;</a></h2>
 <p>In the section on <a href="">launching</a> the framework above, the <code>Felix</code> class accepts a configuration property called <code>felix.systembundle.activators</code>, which is a list of bundle activator instances. These bundle activator instances provide a convenient way for host applications to interact with the Felix framework.</p>
 <div class="warning" markdown="1">
 **WARNING**
@@ -497,7 +519,7 @@ The `felix.systembundle.activators` conf
 
 
 <p>Notice how the <code>HostApplication.getInstalledBundles()</code> method uses its activator instance to get access to the system bundle's context in order to interact with the embedded Felix framework instance. This approach provides the foundation for all interaction between the host application and the embedded framework instance.</p>
-<h2 id="providing-host-application-services">Providing Host Application Services</h2>
+<h2 id="providing-host-application-services">Providing Host Application Services<a class="headerlink" href="#providing-host-application-services" title="Permanent link">&para;</a></h2>
 <p>Providing services from the host application to bundles inside the embedded Felix framework instance follows the basic approach laid out in <a href="">above</a>. The main complication for providing a host application service to bundles is the fact that both the host application and the bundles must be using the same class definitions for the service interface classes. Since the host application cannot import classes from a bundle, this means that the service interface classes <em>must</em> be accessible on the class path, typically as part of the host application itself. The host application then must export the service interface package via the system bundle so that bundles installed into the embedded framework instance can import it. This is achieved using the <code>org.osgi.framework.system.packages.extra</code> configuration property previously presented.</p>
 <p>Consider the follow simple property lookup service:</p>
 <div class="codehilite"><pre><span class="n">package</span> <span class="n">host</span><span class="p">.</span><span class="n">service</span><span class="p">.</span><span class="n">lookup</span><span class="p">;</span>
@@ -622,7 +644,7 @@ The `felix.systembundle.activators` conf
 
 
 <p>Rather than having the host application bundle activator register the service, it is also possible for the the host application to simply get the bundle context from the bundle activator and register the service directly, but the presented approach is perhaps a little cleaner since it allows the host application to register/unregister the service when the system bundle starts/stops.</p>
-<h2 id="using-services-provided-by-bundles">Using Services Provided by Bundles</h2>
+<h2 id="using-services-provided-by-bundles">Using Services Provided by Bundles<a class="headerlink" href="#using-services-provided-by-bundles" title="Permanent link">&para;</a></h2>
 <p>Using services provided by bundles follows the same general approach of using a host application bundle activator. The main complication for the host application using a service from a bundle is the fact that both the host application and the bundle must be using the same class definitions for the service interface classes. Since the host application cannot import classes from a bundle, this means that the service interface classes <em>must</em> be accessible on the class path, typically as part of the host application itself. The host application then must export the service interface package via the system bundle so that bundles installed into the embedded framework instance can import it. This is achieved using the <code>org.osgi.framework.system.packages.extra</code> configuration property previously presented.</p>
 <p>Consider the following simple command service interface for which bundles provide implementations, such as might be used to create an extensible interactive shell:</p>
 <div class="codehilite"><pre><span class="n">package</span> <span class="n">host</span><span class="p">.</span><span class="n">service</span><span class="p">.</span><span class="n">command</span><span class="p">;</span>
@@ -752,16 +774,16 @@ The `felix.systembundle.activators` conf
 
 
 <p>The above example is overly simplistic with respect to concurrency issues and error conditions, but it demonstrates the overall approach for using bundle-provided services from the host application.</p>
-<h3 id="using-bundle-services-via-reflection">Using Bundle Services via Reflection</h3>
+<h3 id="using-bundle-services-via-reflection">Using Bundle Services via Reflection<a class="headerlink" href="#using-bundle-services-via-reflection" title="Permanent link">&para;</a></h3>
 <p>It possible for the host application to use services provided by bundles without having access to the service interface classes and thus not needing to put the service interface classes on the class path. To do this, the host application uses the same general approach to acquire the system bundle context object, which it can use to look up service objects. Using either an LDAP filter or the service interface class name, the host application can retrieve the service object and then use standard Java reflection to invoke methods on the service object.</p>
-<h3 id="other-approaches">Other Approaches</h3>
+<h3 id="other-approaches">Other Approaches<a class="headerlink" href="#other-approaches" title="Permanent link">&para;</a></h3>
 <p>The <a href="http://code.google.com/p/transloader/">Transloader</a> project is another attempt at dealing with issues of classes loaded from different class loaders and may be of interest.</p>
-<h1 id="caveat">Caveat</h1>
+<h1 id="caveat">Caveat<a class="headerlink" href="#caveat" title="Permanent link">&para;</a></h1>
 <p>The code in this document has not been thoroughly tested nor even compiled and may be out of date with respect to the current Felix source code. If you find errors please report them so the that they can be corrected.</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="">users-subscribe@felix.apache.org</a>; after subscribing, email questions or feedback to [users@felix.apache.org|mailto:users@felix.apache.org].</p>
       <div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
-        Rev. 1422427 by fmeschbe on Sun, 16 Dec 2012 00:36:51 +0000
+        Rev. 1700393 by cziegeler on Tue, 1 Sep 2015 06:04:06 +0000
       </div>
       <div class="trademarkFooter"> 
         Apache Felix, Felix, Apache, the Apache feather logo, and the Apache Felix project

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 Tue Sep  1 06:05:17 2015
@@ -39,7 +39,18 @@
     </div>
     
     <div class="menu"> 
-      <p><a href="/news.html">news</a>  <br />
+      <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 />
@@ -66,7 +77,18 @@
       </div>
 
       <h1>Apache Felix Framework OSGi R4.2 CT Results</h1>
-      <h1 id="overview">Overview</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="overview">Overview<a class="headerlink" href="#overview" title="Permanent link">&para;</a></h1>
 <p>The following results are for the OSGi R4.2 core framework TCK test suites:</p>
 <ul>
 <li><em>org.osgi.test.cases.framework</em> - Tests framework functionality.
@@ -87,27 +109,27 @@
 <li><em>org.osgi.test.cases.condpermadmin</em> - Test Conditional Permission Admin implementation.</li>
 <li><em>org.osgi.test.cases.permissionadmin</em> - Test Permission Admin implementation.</li>
 </ul>
-<h1 id="results">Results</h1>
+<h1 id="results">Results<a class="headerlink" href="#results" title="Permanent link">&para;</a></h1>
 <p><em>Results from: October 26th, 2010</em></p>
 <p>The results for the test suites are as follows:</p>
 <ul>
 <li><em>org.osgi.test.cases.framework</em>
 <strong> <em>activationpolicy</em>
 <strong><em> PASSED
-<em><em> </em>classloading</em></em></strong> PASSED</strong> <em>classpath</em>
+</em><em> </em>classloading*</strong>* PASSED</strong> <em>classpath</em>
 <strong><em> PASSED
-<em><em> </em>div</em></em></strong> PASSED
+</em><em> </em>div*</strong><em> PASSED
 <strong> <em>dynpkgimport</em>
 <strong><em> PASSED
-<em><em> </em>filter</em></em></strong> PASSED</strong> <em>fragments</em>
+</em><em> </em>filter*</strong>* PASSED</strong> </em>fragments<em>
 <strong><em> PASSED
-<em><em> </em>hooks</em></em></strong> PASSED
+</em><em> </em>hooks*</strong></em> PASSED
 <strong> <em>lifecycle</em>
 <strong><em> PASSED
-<em><em> </em>permissions</em></em></strong> PASSED</strong> <em>resources</em>
+</em><em> </em>permissions*</strong>* PASSED</strong> <em>resources</em>
 <strong><em> PASSED
-<em><em> </em>service</em></em></strong> PASSED
-<strong> <em>syncbundlelistener</em></strong>* PASSED</li>
+</em><em> </em>service*</strong><em> PASSED
+<strong> <em>syncbundlelistener</em></strong></em> PASSED</li>
 <li><em>org.osgi.test.cases.framework.secure</em>
 ** PASSED</li>
 <li><em>org.osgi.test.cases.framework.launch</em>
@@ -127,10 +149,10 @@
 <li><em>org.osgi.test.cases.permissionadmin</em>
 ** PASSED</li>
 </ul>
-<h1 id="certification">Certification</h1>
+<h1 id="certification">Certification<a class="headerlink" href="#certification" title="Permanent link">&para;</a></h1>
 <p>Framework 3.0 plus Framework Security Provider 1.4 have been certified R4.2 compliant and are now listed at the <a href="http://www.osgi.org/Specifications/Certified">OSGi Alliance web site</a>. The information on this page may vary, since its purpose is to track the current status of the trunk against the latest OSGi CT.</p>
       <div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
-        Rev. 1422427 by fmeschbe on Sun, 16 Dec 2012 00:36:51 +0000
+        Rev. 1700393 by cziegeler on Tue, 1 Sep 2015 06:04:06 +0000
       </div>
       <div class="trademarkFooter"> 
         Apache Felix, Felix, Apache, the Apache feather logo, and the Apache Felix project



Mime
View raw message