felix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r963800 [12/16] - in /websites/staging/felix/trunk/content: ./ documentation/ documentation/community/ documentation/development/ documentation/faqs/ documentation/subprojects/ documentation/subprojects/apache-felix-commons/ documentation/s...
Date Tue, 01 Sep 2015 06:05:20 GMT
Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-user-guide/sigil-ivy.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-user-guide/sigil-ivy.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-user-guide/sigil-ivy.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>Sigil Ivy</h1>
-      <h2 id="sigil-ivy-extension">Sigil Ivy Extension</h2>
+      <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>
+<h2 id="sigil-ivy-extension">Sigil Ivy Extension<a class="headerlink" href="#sigil-ivy-extension" title="Permanent link">&para;</a></h2>
 <p><a href="">Quick start</a></p>
 <p><a href="">ivysettings.xml</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-sigil/sigil-user-guide/sigil-ivy/apache-felix-sigil-ivy-quickstart.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-user-guide/sigil-ivy/apache-felix-sigil-ivy-quickstart.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-user-guide/sigil-ivy/apache-felix-sigil-ivy-quickstart.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 Sigil Ivy Quickstart</h1>
-      <div class="toc">
+      <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>
+<div class="toc">
 <ul>
 <li><a href="#overview">Overview</a></li>
 <li><a href="#shared-configuration">Shared Configuration</a><ul>
@@ -85,14 +107,14 @@
 <li><a href="#next-steps">Next Steps</a></li>
 </ul>
 </div>
-<h2 id="overview">Overview</h2>
+<h2 id="overview">Overview<a class="headerlink" href="#overview" title="Permanent link">&para;</a></h2>
 <p>The sigil-ivy-plugin integrates Sigil with <a href="http://ant.apache.org/ivy/">Apache Ivy</a>. If you are not familiar with Ivy, you should visit their [tutorial|http://ant.apache.org/ivy/history/latest-milestone/tutorial.html].</p>
 <p>Sigil provides a custom Ivy resolver, which allows Ivy to resolve dependencies specified as OSGi Package-Imports, rather than as specific jar artifacts. This avoids the duplication and possible error of having to specify build dependencies separately from OSGi runtime dependencies.</p>
 <p>The plugin works by intercepting the ivy.xml parser and dynamically replacing any dependencies with the results of resolving the OSGi Package-Imports specified in sigil.properties. Sigil can resolve dependencies using a local directory of OSGi bundles, or using an <a href="http://www.osgi.org/Repository/">OBR repository</a>.</p>
 <p>The plugin also provides an Ant task to generate (multiple) OSGi bundles from each sigil.properties file using <a href="http://www.aqute.biz/Code/Bnd">Bnd</a>. sigil.properties is similar to .bnd instruction files, but it supports multiple bundles.</p>
 <p>This Quick Start is based on the Ivy <a href="http://ant.apache.org/ivy/history/latest-milestone/tutorial/dependence.html">project dependencies</a> tutorial, modified to use Sigil. The modified example is in <code>example/dependence</code> in the Sigil download.</p>
-<h2 id="shared-configuration">Shared Configuration</h2>
-<h3 id="ivysettingsproperties">ivysettings.properties</h3>
+<h2 id="shared-configuration">Shared Configuration<a class="headerlink" href="#shared-configuration" title="Permanent link">&para;</a></h2>
+<h3 id="ivysettingsproperties">ivysettings.properties<a class="headerlink" href="#ivysettingsproperties" title="Permanent link">&para;</a></h3>
 <p>You will need to change ivy.jar to point to the location of your Ivy jar. If you don't have Ivy, you can download it from http://ant.apache.org/ivy/download.cgi.</p>
 <div class="codehilite"><pre>repository.dir=<span class="cp">${</span><span class="n">ivy</span><span class="o">.</span><span class="n">settings</span><span class="o">.</span><span class="n">dir</span><span class="cp">}</span>/repository
 sigil-ivy-plugin.jar=<span class="cp">${</span><span class="n">ivy</span><span class="o">.</span><span class="n">settings</span><span class="o">.</span><span class="n">dir</span><span class="cp">}</span>/../../../lib/sigil-ivy-plugin.jar
@@ -100,7 +122,7 @@ ivy.jar=/opt/apache-ivy-2.0.0-rc2/ivy-2.
 </pre></div>
 
 
-<h3 id="ivysettingsxml">ivysettings.xml</h3>
+<h3 id="ivysettingsxml">ivysettings.xml<a class="headerlink" href="#ivysettingsxml" title="Permanent link">&para;</a></h3>
 <p>The lines containing "sigil" need to be added to your ivysettings.xml:</p>
 <ul>
 <li><em>classpath</em> - this references the location of the sigil-ivy-plugin.jar</li>
@@ -138,7 +160,7 @@ ivy.jar=/opt/apache-ivy-2.0.0-rc2/ivy-2.
 <p></ivysettings></p>
 </li>
 </ul>
-<h3 id="sigil-reposproperties">sigil-repos.properties</h3>
+<h3 id="sigil-reposproperties">sigil-repos.properties<a class="headerlink" href="#sigil-reposproperties" title="Permanent link">&para;</a></h3>
 <p>This file contains the definition of the Sigil repositories. It is referenced via the config attribute on the sigil-resolver in ivysettings.xml.</p>
 <p>The repositories defined are:</p>
 <ul>
@@ -165,8 +187,8 @@ ivy.jar=/opt/apache-ivy-2.0.0-rc2/ivy-2.
 </pre></div>
 
 
-<h2 id="project-configuration">Project Configuration</h2>
-<h3 id="buildxml">build.xml</h3>
+<h2 id="project-configuration">Project Configuration<a class="headerlink" href="#project-configuration" title="Permanent link">&para;</a></h2>
+<h3 id="buildxml">build.xml<a class="headerlink" href="#buildxml" title="Permanent link">&para;</a></h3>
 <p>The sigil-ivy-plugin provides an Ant task to build bundles using Bnd. It requires bndlib.jar, which is on the manifest Class-Path, so you don't need to explicitly add bndlib.jar to the classpath, as long as it is present in the same directory as sigil-ivy-plugin.jar.</p>
 <div class="codehilite"><pre><span class="nt">&lt;taskdef</span> <span class="na">name=</span><span class="s">&quot;sigil.bundle&quot;</span>
     <span class="na">classname=</span><span class="s">&quot;org.cauldron.bld.ant.BundleTask&quot;</span>
@@ -179,7 +201,7 @@ ivy.jar=/opt/apache-ivy-2.0.0-rc2/ivy-2.
 </pre></div>
 
 
-<h3 id="ivyxml">ivy.xml</h3>
+<h3 id="ivyxml">ivy.xml<a class="headerlink" href="#ivyxml" title="Permanent link">&para;</a></h3>
 <p>The ivy.xml for the dependee project is unchanged (but, by default, Sigil ignores any dependences it contains).</p>
 <div class="codehilite"><pre><span class="nt">&lt;ivy-module</span> <span class="na">version=</span><span class="s">&quot;1.0&quot;</span><span class="nt">&gt;</span>
     <span class="nt">&lt;info</span> <span class="na">organisation=</span><span class="s">&quot;org.apache&quot;</span> <span class="na">module=</span><span class="s">&quot;dependee&quot;</span><span class="nt">/&gt;</span>
@@ -190,7 +212,7 @@ ivy.jar=/opt/apache-ivy-2.0.0-rc2/ivy-2.
 </pre></div>
 
 
-<h3 id="sigilproperties">sigil.properties</h3>
+<h3 id="sigilproperties">sigil.properties<a class="headerlink" href="#sigilproperties" title="Permanent link">&para;</a></h3>
 <p>Placing a sigil.properties file next to an ivy.xml file, causes the sigil-parser to dynamically replace the dependencies contained in ivy.xml with dependencies determined from the -imports property in sigil.properties.</p>
 <div class="codehilite"><pre><span class="c"># dependee sigil.properties</span>
 
@@ -208,7 +230,7 @@ ivy.jar=/opt/apache-ivy-2.0.0-rc2/ivy-2.
 </pre></div>
 
 
-<h2 id="project-build">Project Build</h2>
+<h2 id="project-build">Project Build<a class="headerlink" href="#project-build" title="Permanent link">&para;</a></h2>
 <p>{code:bgColor=#FFFFCE}
 $ cd dependee
 $ ant jar
@@ -319,10 +341,10 @@ $ <span class="n">ant</span> <span class
 
 
 <p>Notice that the additional dependencies have been resolved against the OBR repository. The warning from Bnd, is because those additional imports are not actually used.</p>
-<h2 id="next-steps">Next Steps</h2>
+<h2 id="next-steps">Next Steps<a class="headerlink" href="#next-steps" title="Permanent link">&para;</a></h2>
 <p>This Quick Start has shown how easily Sigil can integrate with existing Ivy builds. You should now examine the other examples, which give more details of the Sigil configuration and show some real-world examples.</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-sigil/sigil-user-guide/sigil-ivy/apache-felix-sigil-ivy-settings.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-user-guide/sigil-ivy/apache-felix-sigil-ivy-settings.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-user-guide/sigil-ivy/apache-felix-sigil-ivy-settings.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,8 +77,19 @@
       </div>
 
       <h1>Apache Felix Sigil Ivy Settings</h1>
-      <p>The following items in ivysetting.xml need to be configured for Sigil.</p>
-<h2 id="sigil-parser">Sigil Parser</h2>
+      <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 following items in ivysetting.xml need to be configured for Sigil.</p>
+<h2 id="sigil-parser">Sigil Parser<a class="headerlink" href="#sigil-parser" title="Permanent link">&para;</a></h2>
 <p>The sigil-parser takes the following optional attributes:</p>
 <ul>
 <li><em>delegateType</em> the parser type that Sigil delegates to; default it the ivy parser.</li>
@@ -95,7 +117,7 @@ This is only needed when a delegate pars
   </parsers></p>
 </li>
 </ul>
-<h2 id="sigil-resolver">Sigil Resolver</h2>
+<h2 id="sigil-resolver">Sigil Resolver<a class="headerlink" href="#sigil-resolver" title="Permanent link">&para;</a></h2>
 <p>The sigil-resolver takes two mandatory attributes:</p>
 <ul>
 <li><em>name</em> the resolver name</li>
@@ -108,7 +130,7 @@ This is only needed when a delegate pars
 </resolvers></p>
 </li>
 </ul>
-<h2 id="modules">Modules</h2>
+<h2 id="modules">Modules<a class="headerlink" href="#modules" title="Permanent link">&para;</a></h2>
 <p>Sigil injects dependencies with <code>organisation="sigil"</code>. You need to ensure that Ivy uses the sigil-resolver to resolve such dependecies:</p>
 <div class="codehilite"><pre><span class="nt">&lt;modules&gt;</span>
     <span class="nt">&lt;module</span> <span class="na">organisation=</span><span class="s">&quot;sigil&quot;</span> <span class="na">name=</span><span class="s">&quot;.*&quot;</span> <span class="na">resolver=</span><span class="s">&quot;sigil&quot;</span> <span class="nt">/&gt;</span>
@@ -116,7 +138,7 @@ This is only needed when a delegate pars
 <span class="nt">&lt;/modules&gt;</span>
 </pre></div>
       <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-sigil/sigil-user-guide/sigil-junit.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-user-guide/sigil-junit.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-user-guide/sigil-junit.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>Sigil JUnit</h1>
-      <h2 id="overview">Overview</h2>
+      <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>
+<h2 id="overview">Overview<a class="headerlink" href="#overview" title="Permanent link">&para;</a></h2>
 <p>The Sigil JUnit plugin is an OSGi bundle that when started in an OSGi enabled JVM watches for other bundles that contain JUnit TestCase classes in the framework. The main access point to the plugin is the <code>org.cauldron.sigil.junit.server.JUnitService</code>.</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>JUnitService.java|borderStyle=solid</B></DIV><DIV class="codeContent panelContent">
     package org.cauldron.sigil.junit.server;
@@ -101,7 +123,7 @@
 
 When a test is created the `JUnitService` introspects the test class and looks for a method `public void setBundleContext(BundleContext ctx);` if one is found then the BundleContext is injected into the test class before being returned to the caller.
       <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-sigil/sigil-user-guide/sigil-projects.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-user-guide/sigil-projects.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-user-guide/sigil-projects.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>Sigil Projects</h1>
-      <h1 id="sigil-projects">Sigil Projects</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="sigil-projects">Sigil Projects<a class="headerlink" href="#sigil-projects" title="Permanent link">&para;</a></h1>
 <p>This page is meant as an overview of how to set up sigil projects, for an in depth look at the file format see <a href="/documentation/subprojects/apache-felix-sigil/sigil-user-guide/sigil-properties.html">Sigil Properties</a>.</p>
-<h3 id="basics">Basics</h3>
+<h3 id="basics">Basics<a class="headerlink" href="#basics" title="Permanent link">&para;</a></h3>
 <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>sigil.properties</B></DIV><DIV class="codeContent panelContent">
     -bundles: org.foo
     -version: 1.0.0
@@ -124,7 +146,7 @@ Then we could change our sigil.propertie
 
 Where the bundle version and the import range is inherited from the package;org.foo.api property from the parent sigil-defaults.properties file.
       <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-sigil/sigil-user-guide/sigil-properties.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-user-guide/sigil-properties.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-user-guide/sigil-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>Sigil Properties</h1>
-      <h2 id="overview">Overview</h2>
+      <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>
+<h2 id="overview">Overview<a class="headerlink" href="#overview" title="Permanent link">&para;</a></h2>
 <p>sigil.properties is the common configuration file used in both the Eclipse and Ivy plugins. It is also used for the repository configuration (sigil-repos.properties).</p>
 <p>It supports 4 types of property:</p>
 <ul>
@@ -86,8 +108,8 @@
 <p>The sub-property type allows values to be set that are groups of properties. The key prefix before ';' identifies the sub-property name. All keys with the same prefix contribute to the sub-property value.</p>
 <p>The -defaults mechanism allows projects to share common bundle headers and default package import versions.</p>
 <p>Most values are passed to <a href="http://www.aqute.biz/Code/Bnd">Bnd</a>, so Bnd syntax can usually be used, for example: -resources: @lib, to embed a library.</p>
-<h2 id="reference">Reference</h2>
-<table>
+<h2 id="reference">Reference<a class="headerlink" href="#reference" title="Permanent link">&para;</a></h2>
+<table class="table">
 <thead>
 <tr>
 <th>Name</th>
@@ -154,7 +176,7 @@
 <tr>
 <td>-resources</td>
 <td>list</td>
-<td>Specify additional resources to add to bundle. Supports BND use of {} to filter files and @name.jar to embed jar from classpath.</td>
+<td>Specify additional resources to add to bundle. Supports BND use of </td>
 </tr>
 <tr>
 <td>-exports</td>
@@ -219,7 +241,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-sigil/sigil-user-guide/sigil-repositories.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-user-guide/sigil-repositories.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-user-guide/sigil-repositories.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,13 +77,24 @@
       </div>
 
       <h1>Sigil Repositories</h1>
-      <p>Repositories are where the external dependencies for your project live. Sigil resolves and downloads dependencies for OSGi bundles via an extensible repository interface.</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>Repositories are where the external dependencies for your project live. Sigil resolves and downloads dependencies for OSGi bundles via an extensible repository interface.</p>
 <p>Current implementations provided in Sigil are:
 <em> <a href="/documentation/subprojects/apache-felix-sigil/sigil-user-guide/sigil-repositories/apache-felix-sigil-filesystem.html">Apache Felix Sigil Filesystem</a>
 </em> <a href="/documentation/subprojects/apache-felix-sigil/sigil-user-guide/sigil-repositories/apache-felix-sigil-obr.html">Apache Felix Sigil OBR</a></p>
 <p>To add a repository to your workspace go to the Eclipse preferences panel (OS specific instructions) then navigate to Sigil -&gt; Repositories. You can add, edit or remove repositories from here.</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-sigil/sigil-user-guide/sigil-repositories/apache-felix-sigil-filesystem.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-user-guide/sigil-repositories/apache-felix-sigil-filesystem.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-user-guide/sigil-repositories/apache-felix-sigil-filesystem.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 Sigil Filesystem</h1>
-      <p>The file system repository looks in a specific directory (optionally recursing through sub directories) to find OSGi bundles</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>The file system repository looks in a specific directory (optionally recursing through sub directories) to find OSGi bundles</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-sigil/sigil-user-guide/sigil-repositories/apache-felix-sigil-obr.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-user-guide/sigil-repositories/apache-felix-sigil-obr.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-user-guide/sigil-repositories/apache-felix-sigil-obr.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 Sigil OBR</h1>
-      <h2 id="overview">Overview</h2>
+      <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>
+<h2 id="overview">Overview<a class="headerlink" href="#overview" title="Permanent link">&para;</a></h2>
 <p>The OSGi Bundle Repository is an XML index to allow external tools to find out what contents an OSGi bundle provides and a link to a location where the bundle can be downloaded.</p>
 <p>You can generate your own repositories using the <a href="http://www.osgi.org/Repository/BIndex">bindex</a> utility from the OSGi Alliance. If you do create your own repository and it's usable by the public let us know and we'll add it to the list below.</p>
-<h2 id="available-repositories">Available Repositories</h2>
+<h2 id="available-repositories">Available Repositories<a class="headerlink" href="#available-repositories" title="Permanent link">&para;</a></h2>
 <p>The following is a list of OBR repositories.
 - Felix Repository</p>
 <div class="codehilite"><pre><span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">felix</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">org</span><span class="o">/</span><span class="n">obr</span><span class="o">/</span><span class="n">releases</span><span class="p">.</span><span class="n">xml</span>
@@ -96,7 +118,7 @@ http://sigil.codecauldron.org/spring-rel
 </li>
 </ul>
       <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-upnp.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-upnp.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-upnp.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,8 +77,19 @@
       </div>
 
       <h1>Apache Felix UPnP</h1>
-      <h1 id="felix-upnp-documentation">Felix UPnP Documentation</h1>
-<h2 id="introductionwzxhzdk0">Introduction&nbsp;</h2>
+      <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="felix-upnp-documentation">Felix UPnP Documentation<a class="headerlink" href="#felix-upnp-documentation" title="Permanent link">&para;</a></h1>
+<h2 id="introduction">Introduction&nbsp;<a class="headerlink" href="#introduction" title="Permanent link">&para;</a></h2>
 <p>The Felix UPnP project provides an implementation of the OSGi UPnP specification (version 1.1) as described in the <a href="http://www.osgi.org/Specifications/HomePage">OSGi Service Compendium (Release 4)</a> . The specification is implemented by the <em>org.apache.felix.upnp.basedriver</em> bundle and it comes with other bundles, which have been developed to ease the writing and testing of UPnP code.</p>
 <p>The OSGi UPnP specification defines a set of interfaces which should be used by the developers in order to write UPnP Devices and UPnP Control Points on the OSGi Service Platform. From the OSGi point of view, UPnP devices are services registered with the framework, thus the different phases of the UPnP protocol stack, as defined in the <a href="http://www.upnp.org/resources/documents/CleanUPnPDA101-20031202s.pdf">UPnP™ Device Architecture (UDA 1.0)</a>, have been mapped to the discovery and notification mechanisms offered by the OSGi framework.</p>
 <p>The specification defines a UPnP Base Driver component that acts as software bridge between UPnP networks and OSGi. Developers writing UPnP code do not need to interact directly with the driver through some API. The driver works in background by exporting the registered services as UPnP devices, and by registering as services the UPnP devices discovered on UPnP networks. However, the Felix UPnP project has defined few additional interfaces, so a base knowledge of the way the UPnP Base Driver works is useful and will help developers to write their code.</p>
@@ -80,7 +102,7 @@
 1. <a href="">Known issues </a>
 1. <a href="">Acknowledgments </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-upnp/upnp-acknowledgments.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-upnp/upnp-acknowledgments.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-upnp/upnp-acknowledgments.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>UPnP Acknowledgments</h1>
-      <h1 id="acknowledgments">Acknowledgments</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="acknowledgments">Acknowledgments<a class="headerlink" href="#acknowledgments" title="Permanent link">&para;</a></h1>
 <p>The Felix UPnP base driver and related bundles were originally developed by the <a href="http://domoware.isti.cnr.it/">Domoware </a> project which targeted the OSGi R3. The driver is based on a modified version of the "UPnP for Java" library released by the [Cyberlink |http://www.cybergarage.org/net/upnp/java/index.html] project. This version, called CyberDomo, is currently maintained by the Domoware project team and aligned to the Cyberlink library regularly.</p>
-<h5 id="known-issues"><a href="/documentation/subprojects/apache-felix-upnp/upnp-known-issues.html">Known Issues</a> &lt;&lt;</h5>
+<h5 id="known-issues"><a href="/documentation/subprojects/apache-felix-upnp/upnp-known-issues.html">Known Issues</a> &lt;&lt;<a class="headerlink" href="#known-issues" title="Permanent link">&para;</a></h5>
       <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-upnp/upnp-driver-architecture.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-upnp/upnp-driver-architecture.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-upnp/upnp-driver-architecture.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>UPnP Driver architecture</h1>
-      <h1 id="overview-of-the-base-driver-architecturewzxhzdk0">Overview of the Base Driver Architecture&nbsp;</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-of-the-base-driver-architecture">Overview of the Base Driver Architecture&nbsp;<a class="headerlink" href="#overview-of-the-base-driver-architecture" title="Permanent link">&para;</a></h1>
 <p>The Figure 4 shows a simplified component view of the base driver. The driver is composed of two components, the <em>exporter</em> and <em>importer</em>; both using the <em>CyberDomo</em> library, which is a modified version of the library released by the <a href="http://www.cybergarage.org/net/upnp/java/index.html">"CyberLink for Java" project</a>, maintained by the [Domoware project|http://domoware.isti.cnr.it/ ]. The library implements a full UPnP stack. The base driver acts as a bridge between OSGi and the UPnP networks .
 !BaseDriverArchitecture.jpg!
 <em>Figure 4</em> The UPnP Base Driver architecture</p>
@@ -91,11 +113,11 @@
 <p>• <em>felix.upnpbase.cyberdomo.net.loopback</em> (default false)
 • <em>felix.upnpbase.cyberdomo.net.onlyIPV4</em> (default true)
 • <em>felix.upnpbase.cyberdomo.net.onlyIPV6</em> (default false)</p>
-<h5 id="getting-started-testing-upnp-devices-upnp-testing-devices"><a href="/documentation/subprojects/apache-felix-upnp/upnp-getting-started.html">Getting Started</a> &lt;&lt; \| &gt;&gt; [Testing UPnP Devices| UPnP Testing Devices]</h5>
+<h5 id="getting-started-testing-upnp-devices-upnp-testing-devices"><a href="/documentation/subprojects/apache-felix-upnp/upnp-getting-started.html">Getting Started</a> &lt;&lt; \| &gt;&gt; [Testing UPnP Devices| UPnP Testing Devices]<a class="headerlink" href="#getting-started-testing-upnp-devices-upnp-testing-devices" title="Permanent link">&para;</a></h5>
 <hr />
 <p>[1]() K. Mills, C. Dabrowski "Adaptive Jitter Control for UPnP M-Search" IEEE International Conference on Communications, 2003. ICC '03. page(s): 1008- 1013 vol.2 </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-upnp/upnp-getting-started.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-upnp/upnp-getting-started.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-upnp/upnp-getting-started.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>UPnP Getting Started</h1>
-      <h1 id="getting-started">Getting Started</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="getting-started">Getting Started<a class="headerlink" href="#getting-started" title="Permanent link">&para;</a></h1>
 <p>Assuming that, as described in <a href="/documentation/development/building-felix.html">Building Felix</a> web page, you have already checked out the Felix project in the $FELIX<em>HOME directory, the Felix UPnP project is located at $FELIX</em>HOME/trunk/upnp directory. The project is organized in different directories shown in Figure 1.</p>
 <p>!UPnP-Project-Structure.jpg!
 <em>Figure 1</em> The Felix UPnP project structure</p>
@@ -78,15 +100,15 @@
 <p>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; d) UPnP BinaryLight |
 <em>Figure 3</em> The GUIs started by the script "upnp.sh.bat"</p>
 <p>The Felix build process by default uses the JDK1.4 as target class library for all the UPnP bundles. The UPnP Base Driver can be built also with the JDK1.3 as target; to this end you have to define the "platform" property in the command line: type "mvn Dplatform=jdk13 install" from the /upnp/basedriver directory. For details on configuring your Eclipse IDE see [3]().</p>
-<h3 id="common-issues">Common Issues</h3>
+<h3 id="common-issues">Common Issues<a class="headerlink" href="#common-issues" title="Permanent link">&para;</a></h3>
 <p>If you experience problems discovering the UPnP devices of your network:
 <em> Check the configuration of your firewalls. UPnP discovery is based on multicast messages over UDP that usually are not filtered by firewalls, on the contrary the XML description of devices is retrieved using HTTP protocol; usually bound to non standard ports which might be blocked. Check whether firewall is active on your host or on the host of the device you want discover.
 </em> Install a loopback interface if needed. The base driver by default is configured for not using the localhost as loopback interface. If you want to run and test UPnP devices on a machine disconnected by any network, you should install and activate a loopback interface. Pay attention to disable the loopback interface when you are connected to a network again, otherwise both interfaces will be used to expose the UPnP services registered with the framework.</p>
-<h5 id="introduction-overview-of-the-base-driver-architectureupnp-driver-architecture"><a href="/documentation/subprojects/apache-felix-upnp.html">Introduction </a> &lt;&lt; \| &gt;&gt; [Overview of the Base Driver Architecture|UPnP Driver architecture]</h5>
+<h5 id="introduction-overview-of-the-base-driver-architectureupnp-driver-architecture"><a href="/documentation/subprojects/apache-felix-upnp.html">Introduction </a> &lt;&lt; \| &gt;&gt; [Overview of the Base Driver Architecture|UPnP Driver architecture]<a class="headerlink" href="#introduction-overview-of-the-base-driver-architectureupnp-driver-architecture" title="Permanent link">&para;</a></h5>
 <hr />
 <p>[1]() The actual version of the bundles may be different</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-upnp/upnp-known-issues.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-upnp/upnp-known-issues.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-upnp/upnp-known-issues.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>UPnP Known Issues</h1>
-      <h1 id="known-issues">Known issues</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="known-issues">Known issues<a class="headerlink" href="#known-issues" title="Permanent link">&para;</a></h1>
 <p>Currently the bundle does not support the following requirements:
 <em> upnp.ssdp.address Configuration Service
 </em> exported device changes: if a service already exported as UPnP Device changes its own configuration, i.e.: implements new service, changes the friendly name, etc., the new service description is not reflected on the UPnP Device
 <em> icons for exported device are not tested
 </em> no localization support</p>
-<h5 id="writing-upnp-devices-and-control-points-acknowledgments-upnp-acknowledgments"><a href="/documentation/subprojects/apache-felix-upnp/upnp-testing-devices/upnp-examples/upnp-writing-cd-and-cp.html">Writing UPnP Devices and Control Points</a> &lt;&lt; | &gt;&gt; [Acknowledgments |UPnP Acknowledgments ]</h5>
+<h5 id="writing-upnp-devices-and-control-points-acknowledgments-upnp-acknowledgments"><a href="/documentation/subprojects/apache-felix-upnp/upnp-testing-devices/upnp-examples/upnp-writing-cd-and-cp.html">Writing UPnP Devices and Control Points</a> &lt;&lt; | &gt;&gt; [Acknowledgments |UPnP Acknowledgments ]<a class="headerlink" href="#writing-upnp-devices-and-control-points-acknowledgments-upnp-acknowledgments" title="Permanent link">&para;</a></h5>
       <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-upnp/upnp-testing-devices.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-upnp/upnp-testing-devices.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-upnp/upnp-testing-devices.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>UPnP Testing Devices</h1>
-      <h1 id="testing-upnp-deviceswzxhzdk0">Testing UPnP devices&nbsp;</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="testing-upnp-devices">Testing UPnP devices&nbsp;<a class="headerlink" href="#testing-upnp-devices" title="Permanent link">&para;</a></h1>
 <p>The <em>org.apache.felix.upnp.tester</em> bundle installs a component that shows the UPnP devices registered with the OSGi framework. It provides a GUI shown in the Figure 6 that can be used for controlling the discovered devices: by invoking actions and by subscribing for the state variable changes occurring on them.</p>
 <p>!TesterGUI.jpg!
 Figure6 The UPnP Tester GUI</p>
@@ -88,9 +110,9 @@ Figure6 The UPnP Tester GUI</p>
 </em> The "Felix Logger" and "Cyber Debugger" menus enable displaying of the messages received and sent by the base driver (i.e. the content of the UDP communication).
 <em> The "Print Pending Devices" is a utility menu to verify whether incomplete hierarchy of embedded devices have been registered with the framework.
 </em> The "Check Errata UPnPDevices" menu may help the user verify that all the local UPnP Devices have been registered with the mandatory properties, otherwise they would not be exported.</p>
-<h5 id="overview-of-the-base-driver-architecture-the-felix-upnp-examples-upnp-examples"><a href="/documentation/subprojects/apache-felix-upnp/upnp-driver-architecture.html">Overview of the Base Driver Architecture</a> &lt;&lt; \| &gt;&gt; [The Felix UPnP Examples| UPnP Examples]</h5>
+<h5 id="overview-of-the-base-driver-architecture-the-felix-upnp-examples-upnp-examples"><a href="/documentation/subprojects/apache-felix-upnp/upnp-driver-architecture.html">Overview of the Base Driver Architecture</a> &lt;&lt; \| &gt;&gt; [The Felix UPnP Examples| UPnP Examples]<a class="headerlink" href="#overview-of-the-base-driver-architecture-the-felix-upnp-examples-upnp-examples" title="Permanent link">&para;</a></h5>
       <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-upnp/upnp-testing-devices/upnp-examples.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-upnp/upnp-testing-devices/upnp-examples.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-upnp/upnp-testing-devices/upnp-examples.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,22 +77,33 @@
       </div>
 
       <h1>UPnP Examples</h1>
-      <h1 id="the-felix-upnp-examples">The Felix UPnP Examples</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="the-felix-upnp-examples">The Felix UPnP Examples<a class="headerlink" href="#the-felix-upnp-examples" title="Permanent link">&para;</a></h1>
 <p>The UPnP examples released by the UPnP project are simple UPnP devices developed as a proof of concept. The first two examples, the TV and Clock, are used to check the importing and exporting capabilities of the base driver. The third one, the Binary Light, implements a standard UPnP DCP and provides additionally a UPnP presentation page.</p>
-<h2 id="sample-tv-and-clock">Sample TV and Clock</h2>
+<h2 id="sample-tv-and-clock">Sample TV and Clock<a class="headerlink" href="#sample-tv-and-clock" title="Permanent link">&para;</a></h2>
 <p>These devices are dual version of the sample devices developed by the project "Cyberlink for Java" by Satoshi Konno. They have been rewritten according to the OSGi specification and can be used to check the importing and exporting capabilities of the base driver. The simulated TV screen is used to show the messages received by the Clock device and other simulated device like the Air Conditionator and Washing Machine. When launching the original version of such devices you will see that the Felix TV running on the OSGi platform is able to receive the messages from UPnP devices running on different platform and imported in OSGi. At the same time, the Cyberlink TV is able to receive the time event generated by the Felix Clock device and exported by the base driver.
 | !FelixUPnPTV.jpg! | !FelixClock.jpg! |
 | <em>Figure 7</em> The Felix UPnP TV GUI | <em>Figure 8</em> The Felix UPnP Clock GUI |
 If you want to avoid installing the Cyberlink devices, you can run a second instance of Felix by clicking on the batch file again. In this case the Felix TV and Clock will be exported and re-imported by both Felix runtimes and you will see a duplicated TV and Clock device on each platform. Notice that you can stop in any moment a device by closing its window. You can start it again from the Felix shell by selecting the respective bundle ID. Starting with two running instances of the Felix Clock, you can stop the first one and the TVs will lose for a moment the time signal. In fact, being subscribed to the Clock device type and not to a specific device instance, they will receive the time event from the remaining device Clock. One TV will be notified from the clock running on the same platform, while the other will receive the events from an imported TV device. As soon as you stop also the second clock device, the Time message will disappear from both the TVs.</p>
-<h2 id="the-binarylight-example">The BinaryLight example</h2>
+<h2 id="the-binarylight-example">The BinaryLight example<a class="headerlink" href="#the-binarylight-example" title="Permanent link">&para;</a></h2>
 <p>The Binary Light device, according the UPnP DCP, shows a graphical interface you can use to switch on/off the light and to simulate the breaking of the lamp bulb. In this last circumstance you can see, by using the Felix UPnPDevice Tester interface, that the values of the "Status" and "Target" variable may be different. While the "Target" variable represents the expected status after invoking the related action, the "Status" variable describes the real status of the Light Device.
 This example, by exploiting the Felix HTTP Service implementation, installs a UPnP presentation page. By code you can retrieve the presentation page URL by looking for the service property called "UPnP.presentationURL". This property is also visible, as link, through the interface provided by the Tester bundle. Accessing the presentation page by means of a web browser you can switch the light status by clicking on the Light image: the icon on the device windows changes accordingly.
 | !FelixLight.jpg! | !FelixLightBroken.jpg! | !LightPresentationPage.jpg! |
 <em>Figure 9</em> The BinaryLight  GUI and the presentation page</p>
 <p>The source code for the Binary light is slightly different from the one for TV and Clock code because it has been written starting from a Light model which notifies its changes through the PropertyChangeListener interface. </p>
-<h5 id="testing-upnp-devices-writing-upnp-devices-and-control-points-upnp-writing-cd-and-cp"><a href="/documentation/subprojects/apache-felix-upnp/upnp-testing-devices.html">Testing UPnP Devices</a> &lt;&lt; \| &gt;&gt; [Writing UPnP Devices and Control Points| UPnP Writing CD and CP]</h5>
+<h5 id="testing-upnp-devices-writing-upnp-devices-and-control-points-upnp-writing-cd-and-cp"><a href="/documentation/subprojects/apache-felix-upnp/upnp-testing-devices.html">Testing UPnP Devices</a> &lt;&lt; \| &gt;&gt; [Writing UPnP Devices and Control Points| UPnP Writing CD and CP]<a class="headerlink" href="#testing-upnp-devices-writing-upnp-devices-and-control-points-upnp-writing-cd-and-cp" title="Permanent link">&para;</a></h5>
       <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-upnp/upnp-testing-devices/upnp-examples/upnp-writing-cd-and-cp.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-upnp/upnp-testing-devices/upnp-examples/upnp-writing-cd-and-cp.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-upnp/upnp-testing-devices/upnp-examples/upnp-writing-cd-and-cp.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>UPnP Writing CD and CP</h1>
-      <h1 id="writing-upnp-devices-and-control-points">Writing UPnP Devices and Control Points</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="writing-upnp-devices-and-control-points">Writing UPnP Devices and Control Points<a class="headerlink" href="#writing-upnp-devices-and-control-points" title="Permanent link">&para;</a></h1>
 <p>The <a href="http://www.osgi.org/Specifications/HomePage">OSGi UPnP Specification (v 1.1)</a> dedicates section 111.6 "Working with a UPnP Device" to describe the details of implementing UPnP Devices on OSGi. Here we provide some hints on the main differences you may encounter working with OSGi with respect to the [UDA 1.0 Specification|http://www.upnp.org/resources/documents/CleanUPnPDA101-20031202s.pdf] .</p>
 <p>The first peculiarity is that OSGi provides a centralized register for discovering of UPnP devices as opposed to the distributed mechanism of the UPnP protocol stack. Thus, while in the UPnP networks the steps for subscribing the services of some device are typically 1) <em>discover</em> the required device and 2) <em>subscribe</em> the service, within the OSGi platform a Control Point may register an interest in receiving notify events even before the device is really plugged on the network. This is possible because the subscription mechanism is based on the <a href="http://www.osgi.org/javadoc/r4/org/osgi/service/upnp/UPnPEventListener.html">UPnPEventListener</a>interface that is used for registering OSGi services, which ultimately handles the notify messages sent by the producers of the events. The base driver (importer) keeps track of such UPnPEventListener services and as soon as a matching service is discovered on the UPnP network, a subscription is made on behalf of the re
 gistered listeners.</p>
 <p>On the other hand, even if it is enough to register a service implementing the <a href="http://www.osgi.org/javadoc/r4/org/osgi/service/upnp/UPnPDevice.html">UPnPDevice</a>interface to expose it as UPnP devices on the network, the developers have to implement on their own the event management required by the UPnP technology. From this point of view, for each evented state variable declared by the UPnP device, the developers have to monitor UPnPEventListenerservices that is error prone[1]. The correct implementation of the UPnP eventing phase is left entirely to developers. In particular, in UDA 1.0, the first time a Control Point subscribes a service, the current value of its state variables should soon be delivered to it. To manage this situation in a standard way, the last OSGi UPnP specification defined the extended interface [UPnPLocalStateVariable|http://www.osgi.org/javadoc/r4/org/osgi/service/upnp/UPnPLocalStateVariable.html]. In fact, the previous basic interface UPnPStat
 eVariable provided only a descriptive interface which did not enable to get the value of a state variable without knowing the final implementation class. Every developer should use this new interface in order to allow the specification of helper classes that ease the subscription/notify management (see [UPnPEventNotifier|http://svn.apache.org/viewvc/felix/trunk/upnp/extra/src/main/java/org/apache/felix/upnp/extra/util/UPnPSubscriber.java?view=markup] below).</p>
 <p>We have factorized and released part of the code used by the UPnP examples with the <em>org.apache.felix.upnp.extra</em> bundle.</p>
-<h2 id="the-extra-bundle-and-the-driver-interfaces">The Extra bundle and the driver interfaces</h2>
+<h2 id="the-extra-bundle-and-the-driver-interfaces">The Extra bundle and the driver interfaces<a class="headerlink" href="#the-extra-bundle-and-the-driver-interfaces" title="Permanent link">&para;</a></h2>
 <p>We provide some utility classes and services through the extra bundle and the services registered by the UPnP Base Driver.</p>
 <p>In the Extra bundle the class <a href="http://svn.apache.org/viewvc/felix/trunk/upnp/extra/src/main/java/org/apache/felix/upnp/extra/util/UPnPSubscriber.java?view=markup">org.apache.felix.upnp.extra.util.UPnPSubscriber</a> can be instantiated to subscribe one or more services. The constructor takes two parameters a [BundleContext |http://www.osgi.org/javadoc/r4/org/osgi/framework/BundleContext.html] reference and a [UPnPEventListener |http://www.osgi.org/javadoc/r4/org/osgi/service/upnp/UPnPEventListener.html] reference. In this class the method subscribe(Filter aFilter) is a general and powerful way to subscribe to any service by using an [LDAP filter|http://www.osgi.org/javadoc/r4/org/osgi/framework/Filter.html]. For example by using the string :</p>
 <div class="codehilite"><pre>&quot;<span class="p">(</span><span class="o">&amp;</span> <span class="p">(</span><span class="n">UPnP</span><span class="p">.</span><span class="n">device</span><span class="p">.</span><span class="n">type</span><span class="p">=</span><span class="n">urn</span><span class="p">:</span><span class="n">schemas</span><span class="o">-</span><span class="n">upnp</span><span class="o">-</span><span class="n">org</span><span class="p">:</span><span class="n">device</span><span class="p">:</span><span class="n">BinaryLight</span><span class="p">:</span>1<span class="p">)</span> <span class="p">(</span><span class="n">UPnP</span><span class="p">.</span><span class="n">service</span><span class="p">.</span><span class="n">type</span><span class="p">=</span> <span class="n">urn</span><span class="p">:</span><span class="n">schemas</span><span class="o">-</span><span class="n">upnp</span><span class="o">-</span><span class="n">org</span><span class="p">:</span><s
 pan class="n">service</span><span class="p">:</span><span class="n">SwitchPower</span><span class="p">:</span>1<span class="p">))</span>&quot;
@@ -110,11 +132,11 @@
 <a href="http://svn.apache.org/viewvc/felix/trunk/upnp/basedriver/src/main/java/org/apache/felix/upnp/basedriver/controller/DriverController.java?view=markup">org.apache.felix.upnp.basedriver.controller.DriverController</a>;</p>
 <p>The former can be used to retrieve the XML description of both devices and services. Other than be used for debugging purpose, it allows access to the UPnP schema extensions defined by UPnP Vendors. According to the UDA 1.0 they consist of elements inserted in different points of the XML description and by convention starting with the prefix "X_". This interface is used by the context menu handler of the UPnP Tester bundle.</p>
 <p>The latter interface can be used to change the log messages of the base driver at runtime. Two different methods are available to modify the log level of the base driver or to enable the visualization of low level messages related to the UPnP stack protocol (CyberDomo). Furthermore, the interface allows developers to send an M-SEARCH discovery message to the UPnP networks, thus refreshing the list of imported devices.</p>
-<h5 id="the-felix-upnp-examples-known-issues-upnp-known-issues"><a href="/documentation/subprojects/apache-felix-upnp/upnp-testing-devices/upnp-examples.html">The Felix UPnP Examples</a> &lt;&lt; \| &gt;&gt; [Known Issues| UPnP Known Issues]</h5>
+<h5 id="the-felix-upnp-examples-known-issues-upnp-known-issues"><a href="/documentation/subprojects/apache-felix-upnp/upnp-testing-devices/upnp-examples.html">The Felix UPnP Examples</a> &lt;&lt; \| &gt;&gt; [Known Issues| UPnP Known Issues]<a class="headerlink" href="#the-felix-upnp-examples-known-issues-upnp-known-issues" title="Permanent link">&para;</a></h5>
 <hr />
 <p>[1]() Developers should monitor UPnpEventListener services with a filter matching either the own service Id or service type, either the own device Id or device type and even a empty filter which are usually used to express interest for every UPnP device.</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-user-admin.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-user-admin.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-user-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,9 +77,20 @@
       </div>
 
       <h1>Apache Felix User Admin</h1>
-      <h1 id="apache-felix-user-admin">Apache Felix User 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-user-admin">Apache Felix User Admin<a class="headerlink" href="#apache-felix-user-admin" title="Permanent link">&para;</a></h1>
 <p>{include:Apache Felix User Admin - Introduction}</p>
-<h2 id="table-of-contents">Table of contents</h2>
+<h2 id="table-of-contents">Table of contents<a class="headerlink" href="#table-of-contents" title="Permanent link">&para;</a></h2>
 <ul>
 <li><a href="/documentation/subprojects/apache-felix-user-admin/apache-felix-user-admin-background.html">Background</a> explains the problem being solved and the main design goals;</li>
 <li><a href="/documentation/subprojects/apache-felix-user-admin/apache-felix-user-admin-getting-started.html">Getting Started</a> helps you with the basic concepts by example;</li>
@@ -77,7 +99,7 @@
 <li><a href="">Writing custom repository stores</a> helps you in writing your own repository store.</li>
 </ul>
       <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-user-admin/apache-felix-user-admin-background.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-user-admin/apache-felix-user-admin-background.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-user-admin/apache-felix-user-admin-background.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,19 +77,30 @@
       </div>
 
       <h1>Apache Felix User Admin - Background</h1>
-      <p>For a detailed overview on the UserAdmin service, see the OSGi compendium specification version 4.0 or later. </p>
-<h2 id="roles">Roles</h2>
+      <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>For a detailed overview on the UserAdmin service, see the OSGi compendium specification version 4.0 or later. </p>
+<h2 id="roles">Roles<a class="headerlink" href="#roles" title="Permanent link">&para;</a></h2>
 <p>The UserAdmin service defines two types of roles: <em>users</em> and <em>groups</em>. Other types of roles are not and cannot be defined.</p>
-<h3 id="users">Users</h3>
+<h3 id="users">Users<a class="headerlink" href="#users" title="Permanent link">&para;</a></h3>
 <p>According to the UserAdmin specification, a <code>User</code> role refers to "??any entity that may have any number of credentials associated with it that it may use to authenticate itself??." Normally, <code>User</code> roles are used to authenticate an initiator of a certain action. Although the name suggests otherwise, a <code>User</code> role can also denote anything other than a human being. Examples of valid <code>User</code> roles are:</p>
 <ul>
 <li>A human being with a username and password;</li>
 <li>A machine with a hostname and SSL-certificate.</li>
 </ul>
-<h3 id="groups">Groups</h3>
+<h3 id="groups">Groups<a class="headerlink" href="#groups" title="Permanent link">&para;</a></h3>
 <p>A group is an aggregation of other users and groups, allowing you to create authorization schemes. Roles are either <em>required</em> or <em>basic</em> members of a group. The basic members of a group define the set of members that can be authorized. This set is further reduced by requiring an initiator of an action to imply all required member of a group. A group can be implied only if it has at least one basic member and at least one required member. </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-user-admin/apache-felix-user-admin-file-store.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-user-admin/apache-felix-user-admin-file-store.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-user-admin/apache-felix-user-admin-file-store.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 User Admin - File Store</h1>
-      <p>The Apache Felix User Admin file store provides a file-based store for use with the Felix UserAdmin service. It uses a binary file-format to persist the role information. This file will always be written in the data area of the bundle and be called "<code>ua_repo.dat</code>".</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>The Apache Felix User Admin file store provides a file-based store for use with the Felix UserAdmin service. It uses a binary file-format to persist the role information. This file will always be written in the data area of the bundle and be called "<code>ua_repo.dat</code>".</p>
 <p>The file-based store service this bundle provides can be configured at runtime by using the service PID "<code>org.apache.felix.useradmin.filestore</code>". The configuration options recognized by this service are:</p>
 <ul>
 <li>"<code>background.write.disabled</code>"; by default, all changes made to the UserAdmin repository are flushed to disk. By setting this value to "<code>true</code>", this no longer will happen for each change, but only when the file-store service is stopped. This value is optional and defaults to "<code>false</code>";</li>
@@ -75,7 +97,7 @@
 </ul>
 <p>Alternatively, one can also supply the above mentioned configuration keys prefixed with "<code>org.apache.felix.useradmin.filestore.</code>" as system properties. For example by adding <code>-Dorg.apache.felix.useradmin.filestore.background.write.disabled=true</code> to your JVM arguments will disable persisting the changes upon each change. However, using system properties will imply that only a single store can be configured on a system (which could be a sensible default for some situations)!</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