felix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r963800 [6/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-ipojo/apache-felix-ipojo-junit4osgi/apache-felix-ipojo-junit4osgi-methods.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-junit4osgi/apache-felix-ipojo-junit4osgi-methods.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-junit4osgi/apache-felix-ipojo-junit4osgi-methods.html Tue Sep  1 06:05:17 2015
@@ -171,15 +171,25 @@
 
     <div class="container">
         <div class="content">
-            <h1 id="osgi-and-friends-methods">OSGi and friends methods</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="osgi-and-friends-methods">OSGi and friends methods<a class="headerlink" href="#osgi-and-friends-methods" title="Permanent link">&para;</a></h1>
 <p><em>Developing OSGi tests can be definitely boring. First, testing is generally not a very exciting experience, but imagine if you have to handle all the OSGi issues in your tests... Don't worry junit4osgi provides methods allowing to interact easily with OSGi!</em></p>
-<p>{div:class=toc}
-[TOC]
-{div}</p>
-<h2 id="osgi-methods">OSGi methods</h2>
+<p div="div">{div:class=toc}
+[TOC]</p>
+<h2 id="osgi-methods">OSGi methods<a class="headerlink" href="#osgi-methods" title="Permanent link">&para;</a></h2>
 <p>junit4osgi test case extends the <code>OSGiTestCase</code> class. This class provides useful methods allowing to find services, get them, get the <code>PackageAdmin</code> service...  The description of these methods can be found afterward.</p>
 <p>The most part of the methods are available statically and non-statically. Static methods require a <code>Bundle</code>. Non static methods use the current bundle context, and track get services to release them when the test is done. So, we advise you to use the non-static methods. Static methods just allow you to check that a specific bundle can access to services / resources.</p>
-<h3 id="service-interaction">Service interaction</h3>
+<h3 id="service-interaction">Service interaction<a class="headerlink" href="#service-interaction" title="Permanent link">&para;</a></h3>
 <ul>
 <li><code>boolean isServiceAvailable(String svc)</code> : returns <code>true</code> if the service <code>svc</code> is available.</li>
 <li>
@@ -204,11 +214,11 @@
 <p><code>void waitForService(String itf, String filter, long timeout)</code>: waits for a service arrival matching with the \&lt;service interface, filter> request. If the timeout expires, this method fails. </p>
 </li>
 </ul>
-<h3 id="get-the-bundle-context">Get the bundle context</h3>
+<h3 id="get-the-bundle-context">Get the bundle context<a class="headerlink" href="#get-the-bundle-context" title="Permanent link">&para;</a></h3>
 <ul>
 <li><code>BundleContext getContext()</code> : gives access to the OSGiTestCase bundle context.</li>
 </ul>
-<h3 id="installstartuninstall-bundles">Install/Start/Uninstall bundles</h3>
+<h3 id="installstartuninstall-bundles">Install/Start/Uninstall bundles<a class="headerlink" href="#installstartuninstall-bundles" title="Permanent link">&para;</a></h3>
 <ul>
 <li><code>Bundle installBundle(String url)</code>: installs a bundle from the given url. This method fails if the bundle cannot be installed.</li>
 <li><code>Bundle installBundle(String url, InputStream stream)</code>: installs a bundle from the given input stream. This methods fails if the bundle cannot be installed.</li>
@@ -217,12 +227,12 @@
 <li><code>Bundle getBundle(long bundleId)</code>: gets an installed bundle by its bundle id, or <code>null</code> if not found.</li>
 <li><code>Bundle getBundle(String name)</code>: gets an installed bundle by its symbolic name. Fails if not found.</li>
 </ul>
-<h3 id="packageadmin">PackageAdmin</h3>
+<h3 id="packageadmin">PackageAdmin<a class="headerlink" href="#packageadmin" title="Permanent link">&para;</a></h3>
 <ul>
 <li><code>PackageAdmin getPackageAdmin()</code>: gives access to the <code>Package Admin</code> service exposed by the framework.</li>
 <li><code>refresh()</code>: refresh package wires.</li>
 </ul>
-<h2 id="extensibility-helper-objects">Extensibility: Helper objects</h2>
+<h2 id="extensibility-helper-objects">Extensibility: Helper objects<a class="headerlink" href="#extensibility-helper-objects" title="Permanent link">&para;</a></h2>
 <p>junit4osgi provides an extensibility mechanism to reduce the pain of testing. So, if you're interacting with specific services or environment, you can use <code>Helper</code> objects. Those object have to be created in the <code>setUp</code> method and <code>disposed</code> in the <code>tearDown</code> method. </p>
 <p>So, for example, if you write iPOJO tests, you can use the iPOJO helper providing a lot of utility functions simplifying the development of tests.
 {code:java}
@@ -261,7 +271,7 @@ public class MyTest extends OSGiTestCase
                 may be trademarks or registered trademarks of their respective owners.
                 </div>
                 <div class="timestamp span3 offset2">
-                Rev. 1441864 by fmeschbe on Sun, 3 Feb 2013 06:44:40 +0000
+                Rev. 1700393 by cziegeler on Tue, 1 Sep 2015 06:04:06 +0000
                 </div>
             </div>
         </footer>

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-junit4osgi/apache-felix-ipojo-junit4osgi-tutorial.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-junit4osgi/apache-felix-ipojo-junit4osgi-tutorial.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-junit4osgi/apache-felix-ipojo-junit4osgi-tutorial.html Tue Sep  1 06:05:17 2015
@@ -171,14 +171,24 @@
 
     <div class="container">
         <div class="content">
-            <h1 id="junit4osgi-quick-start">junit4osgi quick start</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="junit4osgi-quick-start">junit4osgi quick start<a class="headerlink" href="#junit4osgi-quick-start" title="Permanent link">&para;</a></h1>
 <p><em>This page describes how using the junit4osgi framework. With the archive tutorial, a pre-configured version of Felix (with the test framework already installed) is also provided.</em></p>
-<p>{div:class=toc}
-[TOC]
-{div}</p>
-<h2 id="getting-junit4osgi">Getting JUnit4OSGi</h2>
+<p div="div">{div:class=toc}
+[TOC]</p>
+<h2 id="getting-junit4osgi">Getting JUnit4OSGi<a class="headerlink" href="#getting-junit4osgi" title="Permanent link">&para;</a></h2>
 <p>The JUnit4OSGi framework is available from the <a href="http://felix.apache.org/site/downloads.cgi">Felix downloads</a>. Source code is also available in the iPOJO sub-project ([sources|Download]). The JUnit4OSGi framework and the different launchers are built when you compile Felix.</p>
-<h2 id="how-to-run-test">How to run test?</h2>
+<h2 id="how-to-run-test">How to run test?<a class="headerlink" href="#how-to-run-test" title="Permanent link">&para;</a></h2>
 <p>Firs of all to execute test you must deploy in your OSGi container:
 1. Your tests
 1. The junit4osgi runtime (executing tests)
@@ -190,7 +200,7 @@
 </strong> To run tests contained in all the test-bundles installed in the framework :<code>junit all</code>
 * The JUnit4OSGi Swing GUI lets you select the test cases and test suites to execute and shows you graphically the result of the tests. You can double-click on a test case result to show its details.</p>
 <p>!http://felix.apache.org/site/apache-felix-ipojo-junit4osgi.data/screenshot-junit4ogsi-swing-runner.PNG!</p>
-<h2 id="testcase-testsuite">TestCase, TestSuite</h2>
+<h2 id="testcase-testsuite">TestCase, TestSuite<a class="headerlink" href="#testcase-testsuite" title="Permanent link">&para;</a></h2>
 <p>A test case is an environment (made of conditions and variables) under which a tester will check that a requirement is satisfied. For JUnit, test cases are classes that define several test methods ; each test method tests an aspect of the targeted requirement. Test cases are often collected into test suites. A test suite aggregates several test cases (and even other test suites), including the notion of test hierarchy. Tests can be organized according to the different requirements they try to validate. The skeleton of a JUnit <code>TestCase</code> and <code>TestSuite</code> is shown just above :</p>
 <div class="codehilite"><pre><span class="cm">/**</span>
 <span class="cm"> * The skeleton of a JUnit test case</span>
@@ -242,7 +252,7 @@
 
 
 <p>First, tests methods are declared in the test case. Their name must begin with "test", so JUnit will execute them on demand. The test are expressed in terms of JUnit assertions ; the <code>assert*()</code> methods causes JUnit test failure if the given assertion is false. The setUp() and tearDown() methods perform specific actions before and after test cases are run. Then, the test suite collect various test cases. It must implement the <code>suite()</code> method that returns the global (and organized) test suite to JUnit.</p>
-<h2 id="osgitestcase-and-osgitestsuite">OSGiTestCase and OSGiTestSuite</h2>
+<h2 id="osgitestcase-and-osgitestsuite">OSGiTestCase and OSGiTestSuite<a class="headerlink" href="#osgitestcase-and-osgitestsuite" title="Permanent link">&para;</a></h2>
 <p>An OSGi test case, is a test case that runs in an OSGi context. <code>OSGiTestCase</code> is the class that all the OSGi test cases you write must extend. This class is a kind of bridge between the JUnit TestCase class and the OSGi environment. The only thing the <code>OSGiTestCase</code> class adds is the access to the bundle context of the bundle containing tests, and some utility methods, giving an easy access to other bundles and services registered in the OSGi framework.</p>
 <p>The structure of an <code>OSGiTestCase</code> is exactly the same as a classic JUnit <code>TestCase</code> :</p>
 <div class="codehilite"><pre> <span class="o">/**</span>
@@ -283,7 +293,7 @@
 </pre></div>
 
 
-<h2 id="how-to-declare-test-suites">How to declare test suites</h2>
+<h2 id="how-to-declare-test-suites">How to declare test suites<a class="headerlink" href="#how-to-declare-test-suites" title="Permanent link">&para;</a></h2>
 <p>This section explains how to declare your test suites in order to expose them to the JUnit4OSGi bundle.</p>
 <p>The written OSGi test suites must be declared by the bundle containing them. To do so, you define add the Test-Suite property in your bundle's header. The following snippets show you how to configure your bundle generation tool to add this property in the header. You can even declare test cases in it. The Junit4OSGi bundle will detect such an header in installed bundle (using the extender pattern) and execute contained tests on demand.</p>
 <p>With the maven-bundle-plugin, add the following lines in your project's pom :</p>
@@ -312,16 +322,16 @@
 </pre></div>
 
 
-<h2 id="quick-examples">Quick examples</h2>
+<h2 id="quick-examples">Quick examples<a class="headerlink" href="#quick-examples" title="Permanent link">&para;</a></h2>
 <p>The following examples show you how to perform unitary tests on your OSGi platform. The first example recovers the example given in the JUnit Cookbook, "bundlizes" it so tests can be run in an OSGi environment. None of the JUnit4OSGi specific features is used, but it shows how to adapt classic JUnit tests. The second example is more OSGi-oriented, and shows how a unitary test can access to the framework via its bundle context.</p>
 <p>These examples can be downloaded <a href="http://people.apache.org/~clement/ipojo/tutorials/junit4osgi/junit4osgi-tutorial.zip">here</a>.</p>
-<h3 id="bundles-to-deploy-to-use-junit4osgi">Bundles to deploy to use junit4osgi</h3>
+<h3 id="bundles-to-deploy-to-use-junit4osgi">Bundles to deploy to use junit4osgi<a class="headerlink" href="#bundles-to-deploy-to-use-junit4osgi" title="Permanent link">&para;</a></h3>
 <p>If you don't use the archive, you can deploy the junit4osgi framework manually. Here is the list of the bundles to deploy and start:
 <em> org.apache.felix.ipojo-1.6.0.jar: iPOJO Core bundle
 </em> org.apache.felix.ipojo.handler.extender-1.6.0.jar: iPOJO Extender pattern handler
 <em> org.apache.felix.ipojo.junit4osgi-1.1.0-SNAPSHOT.jar: the JUnit4OSGi framework
 </em> org.apache.felix.ipojo.junit4osgi.felix-command-1.1.0-SNAPSHOT.jar: the command line junit4osgi runner</p>
-<h3 id="the-remixed-junit-example">The remixed JUnit example</h3>
+<h3 id="the-remixed-junit-example">The remixed JUnit example<a class="headerlink" href="#the-remixed-junit-example" title="Permanent link">&para;</a></h3>
 <p>This example is a simple conversion of a classic JUnit example derived from the JUnit Cookbook. The test case and the test suite are shown to remind you JUnit principles.</p>
 <div class="codehilite"><pre><span class="n">package</span> <span class="n">junit</span><span class="p">.</span><span class="n">example</span><span class="p">;</span>
 <span class="n">import</span> <span class="n">junit</span><span class="p">.</span><span class="n">framework</span><span class="p">.</span><span class="n">TestCase</span><span class="p">;</span>
@@ -385,7 +395,7 @@
 
 
 <p>As you can see above, all tests have been correctly executed !</p>
-<h2 id="an-osgi-based-junit-example">An OSGi-based JUnit example</h2>
+<h2 id="an-osgi-based-junit-example">An OSGi-based JUnit example<a class="headerlink" href="#an-osgi-based-junit-example" title="Permanent link">&para;</a></h2>
 <p>This example shows you how to interact with the OSGi framework within your tests. The test bundle provide a service (HelloService) and tests its work normally. To get the service reference of the HelloService, it uses the bundle context field of the OSGiTestCase class (named <code>'context'</code>) and interacts with it like any other OSGi bundle does.</p>
 <div class="codehilite"><pre><span class="n">package</span> <span class="n">junit</span><span class="p">.</span><span class="n">example</span><span class="p">;</span>
 
@@ -449,7 +459,7 @@
 </pre></div>
 
 
-<h2 id="simple-right">Simple right?</h2>
+<h2 id="simple-right">Simple right?<a class="headerlink" href="#simple-right" title="Permanent link">&para;</a></h2>
 <p>So now you know everything required to run test inside OSGi. You can start developing your own test. To help you a little bit, junit4osgi provides <a href="/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-junit4osgi/apache-felix-ipojo-junit4osgi-methods.html">utilities methods</a> greatly reducing the amount of code to write in your tests. Moreover, if you're a Maven user, the [maven-junit4osgi-plugin|apache-felix-ipojo-junit4osgi-maven] is made for you. It just runs your test directly during the maven build process.</p>
         </div>
     </div>
@@ -465,7 +475,7 @@
                 may be trademarks or registered trademarks of their respective owners.
                 </div>
                 <div class="timestamp span3 offset2">
-                Rev. 1441864 by fmeschbe on Sun, 3 Feb 2013 06:44:40 +0000
+                Rev. 1700393 by cziegeler on Tue, 1 Sep 2015 06:04:06 +0000
                 </div>
             </div>
         </footer>

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-keypoints.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-keypoints.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-keypoints.html Tue Sep  1 06:05:17 2015
@@ -171,19 +171,30 @@
 
     <div class="container">
         <div class="content">
-            <h1 id="ipojo-key-points">iPOJO Key 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="ipojo-key-points">iPOJO Key Points<a class="headerlink" href="#ipojo-key-points" title="Permanent link">&para;</a></h1>
 <p><em>iPOJO is a service-oriented component model. What</em>'<em>s made iPOJO different? Just read this page.</em></p>
-<h2 id="used">Used</h2>
+<h2 id="used">Used<a class="headerlink" href="#used" title="Permanent link">&para;</a></h2>
 <p>iPOJO is used a several and really heterogeneous domain. iPOJO is today used in mobile phone, in home gateway as well as in JEE servers! Module Fusion also proposes to use iPOJO for enterprise applications. </p>
-<h2 id="philosophy">Philosophy</h2>
+<h2 id="philosophy">Philosophy<a class="headerlink" href="#philosophy" title="Permanent link">&para;</a></h2>
 <p>iPOJO aims to be simple. The proposed development model is definitely simple. Do worry about all the obscured technical service and bindings details, just focus on your code. iPOJO manages the everything for you.
 Moreover, it was designed for the OSGi environment. It places the service concept as a top-level concept providing a better reusability, allowing implementation substitution and managing the dynamism. </p>
-<h2 id="supported">Supported</h2>
+<h2 id="supported">Supported<a class="headerlink" href="#supported" title="Permanent link">&para;</a></h2>
 <p>iPOJO is now supported by different companies and research center such as akquinet, Grenoble University, Bull... </p>
-<h2 id="easy-to-use">Easy to use</h2>
+<h2 id="easy-to-use">Easy to use<a class="headerlink" href="#easy-to-use" title="Permanent link">&para;</a></h2>
 <p>Based on the POJO concept and thanks to its different injection mechanisms, iPOJO allows you to reuse he high majority of your existing code!  The business code does not depend on the OSGi environment or on specific technical services. The container manages everything for you.</p>
 <p>with iPOJO you're free! To describe your component, you have the choice among XML, Annotations or an API.</p>
-<h2 id="reliable-and-efficient">Reliable and Efficient</h2>
+<h2 id="reliable-and-efficient">Reliable and Efficient<a class="headerlink" href="#reliable-and-efficient" title="Permanent link">&para;</a></h2>
 <p>iPOJO relies on:</p>
 <ul>
 <li>An OSGi R4.1 framework</li>
@@ -191,11 +202,11 @@ Moreover, it was designed for the OSGi e
 </ul>
 <p>So, you can use iPOJO on Apache Felix, Eclipse Equinox or any OSGi implementation compliant with the OSGi R4.1 specification. Moreover, iPOJO just relies on J2ME Foundation 1.1 profile. So, you can easily embed it...
 However, this does not limit iPOJO in term of performance. iPOJO is one of the most efficient component models for OSGi.  </p>
-<h2 id="embeddable">Embeddable</h2>
+<h2 id="embeddable">Embeddable<a class="headerlink" href="#embeddable" title="Permanent link">&para;</a></h2>
 <p>As told in the previous section, iPOJO does not required advanced Java Virtual Machine. Moreover its footprint is quite small. iPOJO Core size is only 200Kb ! No more is required to use iPOJO...</p>
-<h2 id="adaptable">Adaptable</h2>
+<h2 id="adaptable">Adaptable<a class="headerlink" href="#adaptable" title="Permanent link">&para;</a></h2>
 <p>iPOJO provides a very simple extensibility mechanism. So, you can extend iPOJO for your own requirement. Just look to the list of available handler (i.e. extension). Almost everything is possible...</p>
-<h2 id="going-further">Going further</h2>
+<h2 id="going-further">Going further<a class="headerlink" href="#going-further" title="Permanent link">&para;</a></h2>
 <ul>
 <li>Want to go further; read the <a href="/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-why-choose-ipojo.html">Why choose iPOJO page</a>.</li>
 <li>Want to try; look at the <a href="/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-gettingstarted/ipojo-in-10-minutes.html">iPOJO in 10 minutes tutorial</a></li>
@@ -215,7 +226,7 @@ However, this does not limit iPOJO in te
                 may be trademarks or registered trademarks of their respective owners.
                 </div>
                 <div class="timestamp span3 offset2">
-                Rev. 1443380 by clement on Thu, 7 Feb 2013 10:01:34 +0000
+                Rev. 1700393 by cziegeler on Tue, 1 Sep 2015 06:04:06 +0000
                 </div>
             </div>
         </footer>

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-successstories.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-successstories.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-successstories.html Tue Sep  1 06:05:17 2015
@@ -171,7 +171,18 @@
 
     <div class="container">
         <div class="content">
-            <h1 id="ipojo-success-stories">iPOJO Success Stories</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="ipojo-success-stories">iPOJO Success Stories<a class="headerlink" href="#ipojo-success-stories" title="Permanent link">&para;</a></h1>
 <p><em>On this page, you will find comments from industrial users of iPOJO. They come from different domains such as home gateways, mobile phones, or enterprise applications.</em></p>
 <p><a id="schneider"></a>
 <blockquote>
@@ -227,7 +238,7 @@ You are using iPOJO, and you want to be
                 may be trademarks or registered trademarks of their respective owners.
                 </div>
                 <div class="timestamp span3 offset2">
-                Rev. 1444764 by clement on Mon, 11 Feb 2013 13:45:07 +0000
+                Rev. 1700393 by cziegeler on Tue, 1 Sep 2015 06:04:06 +0000
                 </div>
             </div>
         </footer>

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-supportedosgi.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-supportedosgi.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-supportedosgi.html Tue Sep  1 06:05:17 2015
@@ -171,7 +171,18 @@
 
     <div class="container">
         <div class="content">
-            <h1 id="supported-osgi-implementations">Supported OSGi Implementations</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="supported-osgi-implementations">Supported OSGi Implementations<a class="headerlink" href="#supported-osgi-implementations" title="Permanent link">&para;</a></h1>
 <p><em>Despite iPOJO is an Apache Felix subproject, it relies only on </em>OSGi R4<em> features. So, it is possible to use it on others OSGi implementations.</em></p>
 <table class="table table-bordered table-striped table-hover">
     <thead>
@@ -250,7 +261,7 @@ Recent version of KF does no more requir
                 may be trademarks or registered trademarks of their respective owners.
                 </div>
                 <div class="timestamp span3 offset2">
-                Rev. 1443380 by clement on Thu, 7 Feb 2013 10:01:34 +0000
+                Rev. 1700393 by cziegeler on Tue, 1 Sep 2015 06:04:06 +0000
                 </div>
             </div>
         </footer>

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-supportedvms.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-supportedvms.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-supportedvms.html Tue Sep  1 06:05:17 2015
@@ -171,7 +171,18 @@
 
     <div class="container">
         <div class="content">
-            <h1 id="supported-java-virtual-machines">Supported Java Virtual Machines</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="supported-java-virtual-machines">Supported Java Virtual Machines<a class="headerlink" href="#supported-java-virtual-machines" title="Permanent link">&para;</a></h1>
 <table class="table table-bordered table-striped table-hover">
     <thead>
         <tr>
@@ -279,7 +290,7 @@ iPOJO 1.6+ uses smart proxy by default.
                 may be trademarks or registered trademarks of their respective owners.
                 </div>
                 <div class="timestamp span3 offset2">
-                Rev. 1443380 by clement on Thu, 7 Feb 2013 10:01:34 +0000
+                Rev. 1700393 by cziegeler on Tue, 1 Sep 2015 06:04:06 +0000
                 </div>
             </div>
         </footer>

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-testing-components.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-testing-components.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-testing-components.html Tue Sep  1 06:05:17 2015
@@ -171,9 +171,20 @@
 
     <div class="container">
         <div class="content">
-            <h1 id="how-to-test-ipojo-components">How to test iPOJO Components</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="how-to-test-ipojo-components">How to test iPOJO Components<a class="headerlink" href="#how-to-test-ipojo-components" title="Permanent link">&para;</a></h1>
 <p>Testing components is a required step in the application development process. This page explains strategies to test iPOJO-based components and applications.</p>
-<h2 id="introduction">Introduction</h2>
+<h2 id="introduction">Introduction<a class="headerlink" href="#introduction" title="Permanent link">&para;</a></h2>
 <p>Basically, we can distinguish 2 types of tests:</p>
 <ul>
 <li>Unitary tests</li>
@@ -181,7 +192,7 @@
 </ul>
 <p>Unitary tests are famous and were popularized with the proliferation of frameworks like <a href="http://junit.org">Junit</a> and [TestNG|http://testng.org/doc/]. These tests check the behavior of classes. More specially, these tests check the method results according to different parameter values. These test are executed outside the execution environment, can use mock object (link) to replace/simulate missing dependencies...</p>
 <p>Integration tests focus on the execution of the application inside the execution environment. It checks the global behavior of a service or an application. In the case of iPOJO, those tests are executed on OSGi. Some dependencies can be also replaced by mock services/objects.</p>
-<h2 id="executing-unitary-tests-on-ipojo-components">Executing unitary tests on iPOJO components</h2>
+<h2 id="executing-unitary-tests-on-ipojo-components">Executing unitary tests on iPOJO components<a class="headerlink" href="#executing-unitary-tests-on-ipojo-components" title="Permanent link">&para;</a></h2>
 <p>Unitary tests allow checking the internal behavior of an iPOJO component. Those tests ignore the injected dependencies and focus only on the business code of the component.</p>
 <p>To test components, you can use Junit. A special constructor setting fields can do the dependency injection. These tests are executed before the bundlelization. </p>
 <p>Let's imagine a maven project.  Unitary tests are placed in the src/test/java folder. You can use mock object as illustrated in the example.  When you launch the <code>mvn clean install</code> command, maven compiles your classes and executes the tests.  If the tests are executed successfully, the build process continues and creates the bundle as follows:</p>
@@ -244,7 +255,7 @@
 </pre></div>
 
 
-<h2 id="executing-integration-tests">Executing integration tests</h2>
+<h2 id="executing-integration-tests">Executing integration tests<a class="headerlink" href="#executing-integration-tests" title="Permanent link">&para;</a></h2>
 <p>We recommend to use Pax Exam 3 to test iPOJO components. More details about pax exam 3 are available <a href="https://ops4j1.jira.com/wiki/display/PAXEXAM3/Pax+Exam">here</a>.</p>
         </div>
     </div>
@@ -260,7 +271,7 @@
                 may be trademarks or registered trademarks of their respective owners.
                 </div>
                 <div class="timestamp span3 offset2">
-                Rev. 1467268 by clement on Fri, 12 Apr 2013 13:42:34 +0000
+                Rev. 1700393 by cziegeler on Tue, 1 Sep 2015 06:04:06 +0000
                 </div>
             </div>
         </footer>

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/apache-felix-ipojo-online-manipulator.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/apache-felix-ipojo-online-manipulator.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/apache-felix-ipojo-online-manipulator.html Tue Sep  1 06:05:17 2015
@@ -171,7 +171,18 @@
 
     <div class="container">
         <div class="content">
-            <h1 id="apache-felix-ipojo-online-manipulator">Apache Felix iPOJO Online Manipulator</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-ipojo-online-manipulator">Apache Felix iPOJO Online Manipulator<a class="headerlink" href="#apache-felix-ipojo-online-manipulator" title="Permanent link">&para;</a></h1>
 <p><em>iPOJO generally requires an additional packaging step to prepare the bundle to be managed by iPOJO. Despite this step doesn't change the class semantic, it can be a little annoying. The online manipulator avoids this offline step!</em></p>
 <div class="toc">
 <ul>
@@ -187,7 +198,7 @@
 </li>
 </ul>
 </div>
-<h2 id="features">Features</h2>
+<h2 id="features">Features<a class="headerlink" href="#features" title="Permanent link">&para;</a></h2>
 <p>iPOJO is based on a bytecode manipulation. This manipulate is <em>safe</em> and does not change the class semantics. Classes can still used after the manipulation without iPOJO. However this manipulation is required for iPOJO management. Generally, this manipulation occurs offline during the packaging time. The online manipulator allows to do this manipulation at install time.</p>
 <p>The online manipulator:</p>
 <ul>
@@ -196,11 +207,11 @@
 <li>supports XSD schema</li>
 </ul>
 <p>This is quite useful if you don't want to add an extra packaging step, and provides the same capabilities as the "regular" way.</p>
-<h2 id="usage">Usage</h2>
+<h2 id="usage">Usage<a class="headerlink" href="#usage" title="Permanent link">&para;</a></h2>
 <p>The online-manipulator is in fact an URL Handler. So, it will process every bundle using a special URL prefix. To use it, just follows the below instructions:</p>
-<h3 id="install-and-start-the-url-handler">Install and Start the URL Handler</h3>
+<h3 id="install-and-start-the-url-handler">Install and Start the URL Handler<a class="headerlink" href="#install-and-start-the-url-handler" title="Permanent link">&para;</a></h3>
 <p>Download and install the iPOJO online manipulator. You can download it from the <a href="http://felix.apache.org/downloads.cgi">Felix download page</a></p>
-<h3 id="install-a-bundle-using-the-ipojo-url-prefix">Install a bundle using the <em>ipojo:</em> URL prefix</h3>
+<h3 id="install-a-bundle-using-the-ipojo-url-prefix">Install a bundle using the <em>ipojo:</em> URL prefix<a class="headerlink" href="#install-a-bundle-using-the-ipojo-url-prefix" title="Permanent link">&para;</a></h3>
 <p>Using the handler is quite easy. When you want to deploy a non-manipulated iPOJO bundle just use an url like</p>
 <div class="codehilite"><pre>install ipojo:file:/.../bundle.jar
 </pre></div>
@@ -212,7 +223,7 @@
 
 
 <p>When using the <code>ipojo:</code> prefix, the OSGi platform delegates the loading to the url handler manipulating the bundle before its installation. This manipulation is exactly the same as the offline manipulation.</p>
-<h2 id="dealing-with-metadata">Dealing with metadata</h2>
+<h2 id="dealing-with-metadata">Dealing with metadata<a class="headerlink" href="#dealing-with-metadata" title="Permanent link">&para;</a></h2>
 <p>If the installed bundle contains a <code>metadata.xml</code> file either in its root or in the <code>META-INF</code> directory, the online manipulator will use it. However, you can also provide an external <code>metadata.xml</code> file by indicating the url of the file like in</p>
 <div class="codehilite"><pre>install ipojo:bundle_url!metadata_url
 </pre></div>
@@ -233,7 +244,7 @@
                 may be trademarks or registered trademarks of their respective owners.
                 </div>
                 <div class="timestamp span3 offset2">
-                Rev. 1465947 by clement on Tue, 9 Apr 2013 09:37:22 +0000
+                Rev. 1700393 by cziegeler on Tue, 1 Sep 2015 06:04:06 +0000
                 </div>
             </div>
         </footer>

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/ipojo-ant-task.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/ipojo-ant-task.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/ipojo-ant-task.html Tue Sep  1 06:05:17 2015
@@ -171,7 +171,18 @@
 
     <div class="container">
         <div class="content">
-            <h1 id="ipojo-ant-task">iPOJO Ant Task</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="ipojo-ant-task">iPOJO Ant Task<a class="headerlink" href="#ipojo-ant-task" title="Permanent link">&para;</a></h1>
 <p><em>iPOJO Ant Task allows automating the iPOJO manipulation process within an Ant build process. This page explains how to use the iPOJO Ant Task and how to combine them with the BND Tasks.</em></p>
 <div class="toc">
 <ul>
@@ -185,9 +196,9 @@
 </li>
 </ul>
 </div>
-<h2 id="downloading-the-ipojo-ant-task">Downloading the iPOJO Ant Task</h2>
+<h2 id="downloading-the-ipojo-ant-task">Downloading the iPOJO Ant Task<a class="headerlink" href="#downloading-the-ipojo-ant-task" title="Permanent link">&para;</a></h2>
 <p>The iPOJO Ant Task can ben downloaded from <a href="http://felix.apache.org/downloads.cgi">here</a>.</p>
-<h2 id="how-to-use-the-ant-task">How to use the Ant Task</h2>
+<h2 id="how-to-use-the-ant-task">How to use the Ant Task<a class="headerlink" href="#how-to-use-the-ant-task" title="Permanent link">&para;</a></h2>
 <p>The iPOJO Ant task take an input bundle and a metadata file and create the final (i.e. manipulated) bundle.
 To use the task declare a target in your build.xml as:</p>
 <div class="codehilite"><pre><span class="nt">&lt;target</span> <span class="na">name=</span><span class="s">&quot;main&quot;</span><span class="nt">&gt;</span>
@@ -205,14 +216,14 @@ To use the task declare a target in your
 
 
 <p>First, define the new task. Then simply use it. The input argument describe the input bundle (must exists) and the metadata argument describes the metadata file (must exist too). The input bundle must be a well-formed bundle.</p>
-<h2 id="ant-task-arguments">Ant Task Arguments</h2>
+<h2 id="ant-task-arguments">Ant Task Arguments<a class="headerlink" href="#ant-task-arguments" title="Permanent link">&para;</a></h2>
 <p>The iPOJO Ant Task as three different arguments:
 <em> Input: describes the input bundle. This argument is mandatory.
 </em> Output: describes the output bundle. This argument is optional. If not present, the output file will be input file.
 <em> Metadata: describes the metadata file. This argument is optional. By default, it tries with a metadata.xml file (in      the same directory as the build.xml file). If the default file is not present, it tries to use only iPOJO annotations.
 </em> IgnoreAnnotations: if set to <code>true</code>, the manipulator skips annotations processing (can reduce significantly the processing time on huge bundle).
 * IgnoreEmbeddedSchemas: if set to <code>true</code>, the manipulator doesn't use embedded XML-Schemas</p>
-<h2 id="combining-the-ipojo-ant-task-and-bnd">Combining the iPOJO Ant Task and BND</h2>
+<h2 id="combining-the-ipojo-ant-task-and-bnd">Combining the iPOJO Ant Task and BND<a class="headerlink" href="#combining-the-ipojo-ant-task-and-bnd" title="Permanent link">&para;</a></h2>
 <p>The iPOJO Ant Task requires an input bundle. BND is a tools simplifying bundle creation. So, it is possible to combine the two tools to create your bundle automatically. The following build.xml shows you an example of combination.</p>
 <div class="codehilite"><pre><span class="nt">&lt;project</span> <span class="na">default=</span><span class="s">&quot;main&quot;</span> <span class="na">basedir=</span><span class="s">&quot;.&quot;</span><span class="nt">&gt;</span>
     <span class="nt">&lt;target</span> <span class="na">name=</span><span class="s">&quot;bnd&quot;</span><span class="nt">&gt;</span>
@@ -272,7 +283,7 @@ To be sure that the BND bundle is alread
 </pre></div>
 
 
-<h2 id="directory-manipulation">Directory manipulation</h2>
+<h2 id="directory-manipulation">Directory manipulation<a class="headerlink" href="#directory-manipulation" title="Permanent link">&para;</a></h2>
 <p>The manipulator can take a directory in input. In this case, classes from this folder is manipulated. You can also set the manifest file location too. Here in an example of configuration using this mode:</p>
 <div class="codehilite"><pre><span class="nt">&lt;target</span> <span class="na">name=</span><span class="s">&quot;manipulate&quot;</span><span class="nt">&gt;</span>      
     <span class="c">&lt;!-- Set the manipulated directory and manifest location --&gt;</span> 
@@ -303,7 +314,7 @@ If not set, the manifest is searched in
                 may be trademarks or registered trademarks of their respective owners.
                 </div>
                 <div class="timestamp span3 offset2">
-                Rev. 1530004 by clement on Mon, 7 Oct 2013 17:16:39 +0000
+                Rev. 1700393 by cziegeler on Tue, 1 Sep 2015 06:04:06 +0000
                 </div>
             </div>
         </footer>

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/ipojo-arch-command.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/ipojo-arch-command.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/ipojo-arch-command.html Tue Sep  1 06:05:17 2015
@@ -171,7 +171,18 @@
 
     <div class="container">
         <div class="content">
-            <h1 id="ipojo-architecture-commands">iPOJO architecture commands</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="ipojo-architecture-commands">iPOJO architecture commands<a class="headerlink" href="#ipojo-architecture-commands" title="Permanent link">&para;</a></h1>
 <p><em>Architecture introspection is required when the system doesn't work as expected. In this case, having a quick access to instances states and interconnection is a stringent requirement. The architecture commands allows getting these data from the Felix Shell, from the Equinox shell and Gogo.</em></p>
 <div class="toc">
 <ul>
@@ -189,9 +200,9 @@
 </li>
 </ul>
 </div>
-<h2 id="installation">Installation</h2>
+<h2 id="installation">Installation<a class="headerlink" href="#installation" title="Permanent link">&para;</a></h2>
 <p>According to your shell, download the adequate bundles from <a href="http://felix.apache.org/downloads.cgi">the Felix download page</a></p>
-<h2 id="gogo">Gogo</h2>
+<h2 id="gogo">Gogo<a class="headerlink" href="#gogo" title="Permanent link">&para;</a></h2>
 <p>The Gogo commands are the following:</p>
 <ul>
 <li><code>ipojo:instances</code> (or just <code>instances</code>) lists the instances and state</li>
@@ -219,7 +230,7 @@ instance component.type<span class="o">=
 </pre></div>
 
 
-<h2 id="equinox-and-felix-shells">Equinox and Felix Shells</h2>
+<h2 id="equinox-and-felix-shells">Equinox and Felix Shells<a class="headerlink" href="#equinox-and-felix-shells" title="Permanent link">&para;</a></h2>
 <p>On Equinox and Felix (old) shell, the command is named <em>arch</em>:</p>
 <ul>
 <li>arch =&gt; displays instances name &amp; state (equivalent to arch -instances)</li>
@@ -228,7 +239,7 @@ instance component.type<span class="o">=
 <li>arch -factory $factory<em>name =&gt; display complete information about the factory $factory</em>name</li>
 <li>arch -handlers =&gt; list available handlers</li>
 </ul>
-<h3 id="examples">Examples</h3>
+<h3 id="examples">Examples<a class="headerlink" href="#examples" title="Permanent link">&para;</a></h3>
 <div class="codehilite"><pre>-&gt; arch
 Instance ArchCommand -&gt; valid
 Instance spell.english.EnglishDictionary-0 -&gt; valid
@@ -247,7 +258,7 @@ instance component.type<span class="o">=
 </pre></div>
 
 
-<h2 id="reading-instance-architecture">Reading instance architecture:</h2>
+<h2 id="reading-instance-architecture">Reading instance architecture:<a class="headerlink" href="#reading-instance-architecture" title="Permanent link">&para;</a></h2>
 <p>Instance architecture is organized as follows:</p>
 <ul>
 <li>On the first line, are displayed the component type (i.e. factory), the instance state (<code>valid</code> or <code>invalid</code>), the bundle from which the instance is created, and the instance name.</li>
@@ -284,7 +295,7 @@ If an instance begins to use a service,
 
 <p>In the previous case, the dependency on <code>spell.services.DictionaryService</code> use the service 41 from the iPOJO instance named <code>spell.english.EnglishDictionary-0</code>
 You can also check created POJO objects (implementation class objet). Here, only one object was created (<code>spell.checker.SpellCheck@e222eb</code>).</p>
-<h2 id="list-available-factories">List available factories</h2>
+<h2 id="list-available-factories">List available factories<a class="headerlink" href="#list-available-factories" title="Permanent link">&para;</a></h2>
 <p>You can access factory list using the <code>factories</code> gogo command or the <code>arch -factories</code> on Felix's shell. For every available (public) factories,the name and the state are displayed. A factory is valid if and only if all required handlers are available.</p>
 <div class="codehilite"><pre>-&gt; arch -factories
 Factory spell.checker.SpellCheck <span class="o">(</span>VALID<span class="o">)</span>
@@ -312,7 +323,7 @@ factory implementation-class<span class=
 
 
 <p>On the first line, you get the implementation class of the type, the state of the factory, the bundle declaring the type and the name of the type. You also get the list of required and missing handlers.</p>
-<h2 id="list-available-handlers">List available handlers</h2>
+<h2 id="list-available-handlers">List available handlers<a class="headerlink" href="#list-available-handlers" title="Permanent link">&para;</a></h2>
 <p>Like listing factories, you can get the list of handlers.</p>
 <div class="codehilite"><pre>-&gt; arch -handlers
 Handler org.apache.felix.ipojo:controller <span class="o">(</span>VALID<span class="o">)</span>
@@ -352,7 +363,7 @@ Handler org.apache.felix.ipojo.handler.w
                 may be trademarks or registered trademarks of their respective owners.
                 </div>
                 <div class="timestamp span3 offset2">
-                Rev. 1530200 by guillaume on Tue, 8 Oct 2013 09:20:55 +0000
+                Rev. 1700393 by cziegeler on Tue, 1 Sep 2015 06:04:06 +0000
                 </div>
             </div>
         </footer>

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/ipojo-karaf-feature.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/ipojo-karaf-feature.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/ipojo-karaf-feature.html Tue Sep  1 06:05:17 2015
@@ -171,15 +171,26 @@
 
     <div class="container">
         <div class="content">
-            <h1 id="ipojo-karaf-features">iPOJO Karaf Features</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="ipojo-karaf-features">iPOJO Karaf Features<a class="headerlink" href="#ipojo-karaf-features" title="Permanent link">&para;</a></h1>
 <p>If you are using <a href="http://karaf.apache.org">Apache Karaf</a>, there is a set of <em>features</em> easing the deployment of iPOJO bundles and related tools on Karaf.</p>
-<h2 id="add-the-features-file">Add the features file</h2>
+<h2 id="add-the-features-file">Add the features file<a class="headerlink" href="#add-the-features-file" title="Permanent link">&para;</a></h2>
 <p>First, launch Karaf and add the <a href="http://repo1.maven.org/maven2/org/apache/felix/org.apache.felix.ipojo.features/1.12.1/org.apache.felix.ipojo.features-1.12.1.xml">iPOJO Feature</a> file:</p>
 <div class="codehilite"><pre>features:addurl http://repo1.maven.org/maven2/org/apache/felix/org.apache.felix.ipojo.features/1.12.1/org.apache.felix.ipojo.features-1.12.1.xml
 </pre></div>
 
 
-<h2 id="installing-features">Installing features:</h2>
+<h2 id="installing-features">Installing features:<a class="headerlink" href="#installing-features" title="Permanent link">&para;</a></h2>
 <p>Several features are available:</p>
 <ul>
 <li><code>ipojo</code>: contains the iPOJO Core Runtime</li>
@@ -204,7 +215,7 @@
                 may be trademarks or registered trademarks of their respective owners.
                 </div>
                 <div class="timestamp span3 offset2">
-                Rev. 1531515 by clement on Sat, 12 Oct 2013 08:32:37 +0000
+                Rev. 1700393 by cziegeler on Tue, 1 Sep 2015 06:04:06 +0000
                 </div>
             </div>
         </footer>

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/ipojo-maven-plug-in.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/ipojo-maven-plug-in.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/ipojo-maven-plug-in.html Tue Sep  1 06:05:17 2015
@@ -171,7 +171,18 @@
 
     <div class="container">
         <div class="content">
-            <h1 id="how-to-use-the-ipojo-maven-plug-in">How to use the iPOJO Maven Plug-in</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="how-to-use-the-ipojo-maven-plug-in">How to use the iPOJO Maven Plug-in<a class="headerlink" href="#how-to-use-the-ipojo-maven-plug-in" title="Permanent link">&para;</a></h1>
 <div class="toc">
 <ul>
 <li><a href="#how-to-use-the-ipojo-maven-plug-in">How to use the iPOJO Maven Plug-in</a><ul>
@@ -184,7 +195,7 @@
 </li>
 </ul>
 </div>
-<h2 id="basic-configuration">Basic configuration</h2>
+<h2 id="basic-configuration">Basic configuration<a class="headerlink" href="#basic-configuration" title="Permanent link">&para;</a></h2>
 <p>To use the iPOJO Maven plug-in, edit the following pom.xml (replace all $XXX elements):</p>
 <div class="codehilite"><pre><span class="nt">&lt;project&gt;</span>
     <span class="nt">&lt;modelVersion&gt;</span>4.0.0<span class="nt">&lt;/modelVersion&gt;</span>
@@ -236,7 +247,7 @@
 
 
 <p>The iPOJO Maven Plug-in is generally used with the BND Maven Plug-in (more details here). However the two configurations are completely separated. So, you can use all BND Maven plug-in features. The iPOJO configuration section can be used as previously written without any changes. However it requires that your metadata file is either inside <code>src/main/ipojo</code> or inside the <code>src/main/resources</code> folder and named "metadata.xml".</p>
-<h2 id="execution">Execution</h2>
+<h2 id="execution">Execution<a class="headerlink" href="#execution" title="Permanent link">&para;</a></h2>
 <p>To manipulate your project, use the "<em>mvn clean install</em>" command. The output should be like:</p>
 <div class="codehilite"><pre><span class="o">[</span>INFO<span class="o">]</span> Scanning <span class="k">for </span>projects...
 <span class="o">[</span>INFO<span class="o">]</span> ----------------------------------------------------------------------------
@@ -278,7 +289,7 @@
 </pre></div>
 
 
-<h2 id="configuration-options">Configuration Options</h2>
+<h2 id="configuration-options">Configuration Options<a class="headerlink" href="#configuration-options" title="Permanent link">&para;</a></h2>
 <p>You can configure the localization of the iPOJO metadata file as following:</p>
 <div class="codehilite"><pre><span class="nt">&lt;plugin&gt;</span>
        <span class="nt">&lt;groupId&gt;</span>org.apache.felix<span class="nt">&lt;/groupId&gt;</span>
@@ -342,7 +353,7 @@ Before the `1.7.0`, the set location was
 </pre></div>
 
 
-<h2 id="generate-the-skeleton-of-your-ipojo-bundle">Generate the skeleton of your iPOJO bundle</h2>
+<h2 id="generate-the-skeleton-of-your-ipojo-bundle">Generate the skeleton of your iPOJO bundle<a class="headerlink" href="#generate-the-skeleton-of-your-ipojo-bundle" title="Permanent link">&para;</a></h2>
 <p>The maven-ipojo-plugin provides a way to generate the skeleton of your project. To generate this structure, just launch the following command:</p>
 <div class="codehilite"><pre>mvn org.apache.maven.plugins:maven-archetype-plugin:generate <span class="se">\</span>
 -DarchetypeArtifactId<span class="o">=</span>maven-ipojo-plugin <span class="se">\</span>
@@ -364,7 +375,7 @@ Before the `1.7.0`, the set location was
 The maven-ipojo-plugin archetype generates a pom file using the latest released version of the maven-ipojo-plugin.
 </div>
 
-<h2 id="describing-ipojo-configuration-in-the-pom-file">Describing iPOJO configuration in the pom file</h2>
+<h2 id="describing-ipojo-configuration-in-the-pom-file">Describing iPOJO configuration in the pom file<a class="headerlink" href="#describing-ipojo-configuration-in-the-pom-file" title="Permanent link">&para;</a></h2>
 <p>It is also possible to describe iPOJO components and instances inside the pom file (avoiding using a externalized file). The configuration can be described in the <code>metadata</code> attribute inside a CDATA block.</p>
 <div class="codehilite"><pre><span class="nt">&lt;plugin&gt;</span>
         <span class="nt">&lt;groupId&gt;</span>org.apache.felix<span class="nt">&lt;/groupId&gt;</span>
@@ -423,7 +434,7 @@ The maven-ipojo-plugin archetype generat
                 may be trademarks or registered trademarks of their respective owners.
                 </div>
                 <div class="timestamp span3 offset2">
-                Rev. 1531524 by clement on Sat, 12 Oct 2013 09:57:48 +0000
+                Rev. 1700393 by cziegeler on Tue, 1 Sep 2015 06:04:06 +0000
                 </div>
             </div>
         </footer>

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/ipojo-webconsole-plugin.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/ipojo-webconsole-plugin.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/ipojo-webconsole-plugin.html Tue Sep  1 06:05:17 2015
@@ -171,7 +171,18 @@
 
     <div class="container">
         <div class="content">
-            <h1 id="ipojo-webconsole-plugin">iPOJO Webconsole Plugin</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="ipojo-webconsole-plugin">iPOJO Webconsole Plugin<a class="headerlink" href="#ipojo-webconsole-plugin" title="Permanent link">&para;</a></h1>
 <p><em>If you like the Apache Felix Web Console, you will be interested by the iPOJO plugin. This plugin gives you all the information about iPOJO instances, factories and handlers deployed on the framework.</em></p>
 <div class="toc">
 <ul>
@@ -182,7 +193,7 @@
 </li>
 </ul>
 </div>
-<h2 id="features">Features</h2>
+<h2 id="features">Features<a class="headerlink" href="#features" title="Permanent link">&para;</a></h2>
 <ul>
 <li>Lists created instances</li>
 <li>Gives details about instances (state, factory, required services, provided services, used instances, and raw architecture)</li>
@@ -191,7 +202,7 @@
 <li>List available handlers</li>
 <li>Instance and Factories are <code>navigable</code>, so you can easily understand the system architecture</li>
 </ul>
-<h2 id="using-the-plugin">Using the plugin</h2>
+<h2 id="using-the-plugin">Using the plugin<a class="headerlink" href="#using-the-plugin" title="Permanent link">&para;</a></h2>
 <p>To use the plugin you need an OSGi platform with:</p>
 <ul>
 <li>a HTTP Service</li>
@@ -256,7 +267,7 @@ START LEVEL 1
                 may be trademarks or registered trademarks of their respective owners.
                 </div>
                 <div class="timestamp span3 offset2">
-                Rev. 1531524 by clement on Sat, 12 Oct 2013 09:57:48 +0000
+                Rev. 1700393 by cziegeler on Tue, 1 Sep 2015 06:04:06 +0000
                 </div>
             </div>
         </footer>

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/junit4osgi.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/junit4osgi.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/junit4osgi.html Tue Sep  1 06:05:17 2015
@@ -171,12 +171,23 @@
 
     <div class="container">
         <div class="content">
-            <h1 id="junit4osgi-executing-unitary-and-integration-test-on-osgi">JUnit4OSGi : Executing Unitary and Integration Test on OSGi</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="junit4osgi-executing-unitary-and-integration-test-on-osgi">JUnit4OSGi : Executing Unitary and Integration Test on OSGi<a class="headerlink" href="#junit4osgi-executing-unitary-and-integration-test-on-osgi" title="Permanent link">&para;</a></h1>
 <p>This page is <em>deprecated</em></p>
 <hr />
-<h2 id="goals">Goals</h2>
+<h2 id="goals">Goals<a class="headerlink" href="#goals" title="Permanent link">&para;</a></h2>
 <p>Executing tests on OSGi became a stringent requirement as several aspects need to be tested. Indeed, modularity, services (and the inherent dynamism) and the business logic need to be tested.  The goal of JUnit4OSGi is to provide an execution gateway in order to test bundles and services.  Instead of injecting mock objects, as provided by regular test frameworks to hide the underlying Executing environment, tests are directly executed on OSGi and so have access to all the features provided by the OSGi framework. This allows developers checking modularity aspect and service dynamism in addition to the business logic.</p>
-<h2 id="principles">Principles</h2>
+<h2 id="principles">Principles<a class="headerlink" href="#principles" title="Permanent link">&para;</a></h2>
 <p>Junit4OSGi is split in several pieces. First the core bundle (Junit4OSGi) contains an extended version of Junit (3.8.1). On the top of this framework, several runners are implemented:
 <em> Immediate runner : launch every available test suite
 </em> Command line runner : Felix command line allowing to choose the test suite(s) to launch
@@ -184,14 +195,14 @@
 </em> Maven runner: a maven plug-in allowing to automate tests during the project build process</p>
 <p>The different runners give a great flexibility to the framework that can be used during the build process or to test an application in a special environment (such as J2ME).
 Test suites and test cases are package inside bundles. Junit4OSGi extend Junit to support OSGi test suite and OSGi test case. These two kinds of test classes are able to use the bundle context of the bundle and so are able to deal with the underlying OSGi framework.</p>
-<h2 id="installing-the-framework">Installing the framework</h2>
+<h2 id="installing-the-framework">Installing the framework<a class="headerlink" href="#installing-the-framework" title="Permanent link">&para;</a></h2>
 <p>Except if you use the maven front end (automating the launch a an OSGi framework (Felix) and deploying required bundles), to launch the Junit framework you need to deploy and start
 <em> <a href="http://people.apache.org/~clement/ipojo/binaries/org.apache.felix.ipojo-0.8.0-SNAPSHOT.jar">iPOJO 0.8.0-SNASPHOT</a>
 </em> <a href="http://people.apache.org/~clement/ipojo/binaries/org.apache.felix.ipojo.handler.extender.pattern-0.8.0-SNAPSHOT.jar">iPOJO Extender Pattern Handler 0.8.0-SNAPSHOT</a>
 <em> <a href="http://people.apache.org/~clement/ipojo/junit4osgi/org.apache.felix.ipojo.junit4osgi-0.8.0-SNAPSHOT.jar">The Junit4OSGi bundle</a>
 </em> One runner such as the <a href="http://people.apache.org/~clement/ipojo/junit4osgi/org.apache.felix.ipojo.junit4osgi.felix-command-0.8.0-SNAPSHOT.jar">Felix command</a> one</p>
 <p>The archive available <a href="http://people.apache.org/~clement/ipojo/junit4osgi/junit4osgi.tutorial.zip">here</a> contains a pre-configured version of Felix with the previously mentionned bundles.</p>
-<h2 id="writing-junit-test-case-and-test-suite">Writing Junit Test Case and Test Suite</h2>
+<h2 id="writing-junit-test-case-and-test-suite">Writing Junit Test Case and Test Suite<a class="headerlink" href="#writing-junit-test-case-and-test-suite" title="Permanent link">&para;</a></h2>
 <p>This section describes briefly how to write test cases and test suites and how they are used by the Junit4OSGi framework. More details are available on the Junit web site <a href="http://www.junit.org/">http://www.junit.org/</a>.</p>
 <p>The Money class was introduced in the Junit tutorial and was implemented as the following:</p>
 <div class="codehilite"><pre><span class="n">package</span> <span class="n">junit</span><span class="p">.</span><span class="n">money</span><span class="p">;</span>
@@ -296,7 +307,7 @@ Start the pre-configured Felix with the
 </pre></div>
 
 
-<h2 id="writing-junit-test-case-and-test-suite-specialized-for-osgi">Writing Junit Test Case and Test Suite specialized for OSGi</h2>
+<h2 id="writing-junit-test-case-and-test-suite-specialized-for-osgi">Writing Junit Test Case and Test Suite specialized for OSGi<a class="headerlink" href="#writing-junit-test-case-and-test-suite-specialized-for-osgi" title="Permanent link">&para;</a></h2>
 <p>The previous example has illustrated how creating thest cases and test suites by using the regular Junit framework. However, junit4osgi has the particularity to support specialized test for OSGi.  For example, imagine the very simple Hello Service implemented by the following class:</p>
 <div class="codehilite"><pre><span class="n">public</span> <span class="n">class</span> <span class="n">HelloProvider</span> <span class="n">implements</span> <span class="n">HelloService</span> <span class="p">{</span>
 
@@ -352,7 +363,7 @@ The execution of these tests follows the
 </em> Start Felix
 <em> Deploy the bundle with the following command: <code>start file:../junit-osgi-example/output/junit-osgi-example.jar</code>
 </em> Execute the test by using the junit command</p>
-<h2 id="maven-front-end-automating-tests-in-your-build-process">Maven front end: automating tests in your build process</h2>
+<h2 id="maven-front-end-automating-tests-in-your-build-process">Maven front end: automating tests in your build process<a class="headerlink" href="#maven-front-end-automating-tests-in-your-build-process" title="Permanent link">&para;</a></h2>
 <p><em>Coming soon</em></p>
         </div>
     </div>
@@ -368,7 +379,7 @@ The execution of these tests follows the
                 may be trademarks or registered trademarks of their respective owners.
                 </div>
                 <div class="timestamp span3 offset2">
-                Rev. 1441864 by fmeschbe on Sun, 3 Feb 2013 06:44:40 +0000
+                Rev. 1700393 by cziegeler on Tue, 1 Sep 2015 06:04:06 +0000
                 </div>
             </div>
         </footer>

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/apache-felix-ipojo-api.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/apache-felix-ipojo-api.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/apache-felix-ipojo-api.html Tue Sep  1 06:05:17 2015
@@ -171,7 +171,18 @@
 
     <div class="container">
         <div class="content">
-            <h1 id="ipojo-api">iPOJO API</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="ipojo-api">iPOJO API<a class="headerlink" href="#ipojo-api" title="Permanent link">&para;</a></h1>
 <p><em>The iPOJO API provides a third way to describe iPOJO components and instances. With the API, you can dynamically create new components types and create instances from them. Your component types are described with a Java API. To use the API, deploy and start the iPOJO-API bundle and the iPOJO core bundle.</em></p>
 <div class="toc">
 <ul>
@@ -201,7 +212,7 @@
 </li>
 </ul>
 </div>
-<h2 id="a-simple-example">A simple example</h2>
+<h2 id="a-simple-example">A simple example<a class="headerlink" href="#a-simple-example" title="Permanent link">&para;</a></h2>
 <p>Let's imagine a simple component providing a service Foo. The following code is the implementation class of our component:</p>
 <div class="codehilite"><pre><span class="kn">package</span> <span class="n">org</span><span class="o">.</span><span class="na">example</span><span class="o">.</span><span class="na">service</span><span class="o">.</span><span class="na">impl</span><span class="o">;</span>
 
@@ -252,20 +263,20 @@
 </pre></div>
 
 
-<h2 id="deploying-the-api">Deploying the API</h2>
+<h2 id="deploying-the-api">Deploying the API<a class="headerlink" href="#deploying-the-api" title="Permanent link">&para;</a></h2>
 <p>Before being able to create component types at runtime, you need to deploy 3 bundles:</p>
 <ul>
 <li>iPOJO (core)</li>
 <li>iPOJO Composite</li>
 <li>iPOJO API</li>
 </ul>
-<h2 id="primitive-component-type-basics">Primitive Component Type basics</h2>
+<h2 id="primitive-component-type-basics">Primitive Component Type basics<a class="headerlink" href="#primitive-component-type-basics" title="Permanent link">&para;</a></h2>
 <p>When you create a new Primitive component type (so, using a Java class as implementation), you must set the bundle context and the class name. Everything else is optional. </p>
 <p>Note about inner classes: iPOJO is based on a bytecode manipulation. The API embeds the manipulator. So, when you initialize the component type, the specified class name is manipulated (if not already manipulated). So, as this force using a customized classloader, inner classes cannot be manipulated. So, inner class injection is not supported with the API.</p>
-<h2 id="immediate-component-validate-and-invalidate-method">Immediate Component, Validate and Invalidate Method</h2>
+<h2 id="immediate-component-validate-and-invalidate-method">Immediate Component, Validate and Invalidate Method<a class="headerlink" href="#immediate-component-validate-and-invalidate-method" title="Permanent link">&para;</a></h2>
 <p>To set the component type as immediate, just call the <code>setImmediate(immediate)</code> method on the primitive component type object. 
 To set validate and invalidate methods, just call the <code>setValidate(method)</code> and <code>setInvalidate(method)</code>. Specify the method name that you want to call in argument. </p>
-<h2 id="declaring-services">Declaring services</h2>
+<h2 id="declaring-services">Declaring services<a class="headerlink" href="#declaring-services" title="Permanent link">&para;</a></h2>
 <p>To declare that a component provides a service, add a new service to your primitive component type.
 The Service object can be configured. By default, it exposed every implemented interface (regular iPOJO behavior). So, you can:</p>
 <ul>
@@ -285,7 +296,7 @@ new PrimitiveComponentType()
     .createInstance();</p>
 </li>
 </ul>
-<h2 id="service-dependencies">Service Dependencies</h2>
+<h2 id="service-dependencies">Service Dependencies<a class="headerlink" href="#service-dependencies" title="Permanent link">&para;</a></h2>
 <p>To declare a service dependency, create and add a Dependency object. The dependency object offers all the iPOJO service dependency features. You can set the injected field and/or bind/unbind methods. Here is an example:</p>
 <div class="codehilite"><pre><span class="k">new</span> <span class="nf">PrimitiveComponentType</span><span class="o">()</span>
     <span class="o">.</span><span class="na">setBundleContext</span><span class="o">(</span><span class="n">context</span><span class="o">)</span>
@@ -299,7 +310,7 @@ new PrimitiveComponentType()
 </pre></div>
 
 
-<h2 id="properties">Properties</h2>
+<h2 id="properties">Properties<a class="headerlink" href="#properties" title="Permanent link">&para;</a></h2>
 <p>Thanks to the <code>addProperty</code> method, you can create component properties. Here is some example of properties:</p>
 <div class="codehilite"><pre><span class="k">new</span> <span class="nf">PrimitiveComponentType</span><span class="o">()</span>
     <span class="o">.</span><span class="na">setBundleContext</span><span class="o">(</span><span class="n">context</span><span class="o">)</span>
@@ -316,7 +327,7 @@ new PrimitiveComponentType()
 </pre></div>
 
 
-<h2 id="temporal-dependencies">Temporal Dependencies</h2>
+<h2 id="temporal-dependencies">Temporal Dependencies<a class="headerlink" href="#temporal-dependencies" title="Permanent link">&para;</a></h2>
 <p>Temporal dependencies are also supported: </p>
 <div class="codehilite"><pre><span class="k">new</span> <span class="nf">PrimitiveComponentType</span><span class="o">()</span>
         <span class="o">.</span><span class="na">setBundleContext</span><span class="o">(</span><span class="n">context</span><span class="o">)</span>
@@ -331,18 +342,18 @@ new PrimitiveComponentType()
 </pre></div>
 
 
-<h2 id="instance-creation">Instance creation</h2>
+<h2 id="instance-creation">Instance creation<a class="headerlink" href="#instance-creation" title="Permanent link">&para;</a></h2>
 <p>The API allows you to create instances from the component type you described. Three differents methods.
 The <code>createInstance()</code> method just creates an instance. The <code>createInstance(String name)</code> method allows to set the instance name. Finally, the <code>createInstance(Dictionary configuration)</code> allows setting the instance configuration. All those methods returns the ComponentInstance object allowing to manage the instance (stop, start, dispose). </p>
-<h2 id="managed-service-and-propagation">Managed Service and Propagation</h2>
+<h2 id="managed-service-and-propagation">Managed Service and Propagation<a class="headerlink" href="#managed-service-and-propagation" title="Permanent link">&para;</a></h2>
 <p>You can enable/disable the property propagation thanks to the <code>setPropagation</code> method on the PrimitiveComponentType object. 
 You can also set the the managed service PID with the <code>setManagedServicePID</code> method. This method should be only use to give a default value of for singleton component. In all other case, the managed service pid has to be provided inside the instance configuration.</p>
-<h2 id="managing-ipojo-factory">Managing iPOJO Factory</h2>
+<h2 id="managing-ipojo-factory">Managing iPOJO Factory<a class="headerlink" href="#managing-ipojo-factory" title="Permanent link">&para;</a></h2>
 <p>Beyond the PrimitiveComponentType, an iPOJO factory is hidden. You can configure this factory to be public or private with the <code>setPublic</code> method. You can also set the name of the factory with the <code>setName</code> method. </p>
 <p>Then, you can access to the Factory object by calling the <code>getFactory</code> method.</p>
-<h2 id="access-to-the-introspection-api">Access to the introspection API</h2>
+<h2 id="access-to-the-introspection-api">Access to the introspection API<a class="headerlink" href="#access-to-the-introspection-api" title="Permanent link">&para;</a></h2>
 <p>The API provides bridge to get access to the iPOJO introspection API. The introspection API allows reconfiguring at runtime an instance (properties, service dependencies...). From Service and Dependency, Property and ServiceProperty objects, call the <code>getXXXDescription</code> method. You must give the instance that you want to introspect in argument. If the lookup success, you get an object allowing reconfiguring the service, dependency or property. </p>
-<h2 id="singleton-component-type">Singleton Component Type</h2>
+<h2 id="singleton-component-type">Singleton Component Type<a class="headerlink" href="#singleton-component-type" title="Permanent link">&para;</a></h2>
 <p>If you are sure to create only one instance of your component type, you can use the singleton component type class. This is a kind of primitive component type, but when you start it (with the <code>create</code> method), it will automatically create an instance.</p>
 <div class="codehilite"><pre> <span class="n">PrimitiveComponentType</span> <span class="n">type</span> <span class="o">=</span> <span class="k">new</span> <span class="n">SingletonComponentType</span><span class="o">()</span>
             <span class="o">.</span><span class="na">setBundleContext</span><span class="o">(</span><span class="n">context</span><span class="o">)</span>
@@ -358,7 +369,7 @@ You can also set the the managed service
 
 <p>The type created with the singleton component type are set to <code>private</code> by default. Instead of calling the <code>start</code> method, you have to call one of the <code>create</code> methods to start the type and create the instance.</p>
 <p>You can also set the contained POJO object by using the <code>setObject</code> method. The given object MUST be compatible with the component implementation class.</p>
-<h2 id="using-external-handlers">Using external handlers</h2>
+<h2 id="using-external-handlers">Using external handlers<a class="headerlink" href="#using-external-handlers" title="Permanent link">&para;</a></h2>
 <p>iPOJO is extensible... So, it makes sense that the API is also extensible. So component type provides a method allowing to add external handler configuration:</p>
 <div class="codehilite"><pre><span class="k">return</span> <span class="k">new</span> <span class="nf">PrimitiveComponentType</span><span class="o">()</span>
         <span class="o">.</span><span class="na">setBundleContext</span><span class="o">(</span><span class="n">context</span><span class="o">)</span>
@@ -439,7 +450,7 @@ You can also set the the managed service
 
 
 <p>The only required method is <code>getElement</code> returning the <code>Element-Attribute</code> structure representing the handler configuration (this uses the internal iPOJO data format). If the metadata cannot be generated, the class throws IllegalStateExceptions.</p>
-<h2 id="creating-compositions-with-the-api">Creating compositions with the API</h2>
+<h2 id="creating-compositions-with-the-api">Creating compositions with the API<a class="headerlink" href="#creating-compositions-with-the-api" title="Permanent link">&para;</a></h2>
 <p>The API also allows you to create iPOJO compositions in a pretty simple way. So you can create compositions:</p>
 <ul>
 <li>containing internal instances</li>
@@ -449,7 +460,7 @@ You can also set the the managed service
 <li>providing services (by delegation)</li>
 </ul>
 <p>Here are some examples:</p>
-<h4 id="creating-instances-inside-a-composite">Creating instances inside a composite:</h4>
+<h4 id="creating-instances-inside-a-composite">Creating instances inside a composite:<a class="headerlink" href="#creating-instances-inside-a-composite" title="Permanent link">&para;</a></h4>
 <div class="codehilite"><pre><span class="n">PrimitiveComponentType</span> <span class="n">prov</span> <span class="o">=</span> <span class="n">createAProvider</span><span class="o">();</span> <span class="c1">// Create a primitive type</span>
 <span class="n">PrimitiveComponentType</span> <span class="n">cons</span> <span class="o">=</span> <span class="n">createAConsumer</span><span class="o">();</span> <span class="c1">// Create another primitive type</span>
 
@@ -463,7 +474,7 @@ You can also set the the managed service
 </pre></div>
 
 
-<h4 id="importing-a-service">Importing a service</h4>
+<h4 id="importing-a-service">Importing a service<a class="headerlink" href="#importing-a-service" title="Permanent link">&para;</a></h4>
 <div class="codehilite"><pre><span class="n">CompositeComponentType</span> <span class="n">type</span> <span class="o">=</span> <span class="k">new</span> <span class="n">CompositeComponentType</span><span class="o">()</span>
        <span class="o">.</span><span class="na">setBundleContext</span><span class="o">(</span><span class="n">context</span><span class="o">)</span>
        <span class="o">.</span><span class="na">setComponentTypeName</span><span class="o">(</span><span class="s">&quot;comp3&quot;</span><span class="o">)</span>
@@ -473,7 +484,7 @@ You can also set the the managed service
 </pre></div>
 
 
-<h4 id="instantiating-a-service">Instantiating a service</h4>
+<h4 id="instantiating-a-service">Instantiating a service<a class="headerlink" href="#instantiating-a-service" title="Permanent link">&para;</a></h4>
 <div class="codehilite"><pre><span class="n">CompositeComponentType</span> <span class="n">type</span> <span class="o">=</span> <span class="k">new</span> <span class="n">CompositeComponentType</span><span class="o">()</span>
        <span class="o">.</span><span class="na">setBundleContext</span><span class="o">(</span><span class="n">context</span><span class="o">)</span>
        <span class="o">.</span><span class="na">setComponentTypeName</span><span class="o">(</span><span class="s">&quot;comp2&quot;</span><span class="o">)</span>
@@ -483,7 +494,7 @@ You can also set the the managed service
 </pre></div>
 
 
-<h4 id="exporting-a-service">Exporting a service</h4>
+<h4 id="exporting-a-service">Exporting a service<a class="headerlink" href="#exporting-a-service" title="Permanent link">&para;</a></h4>
 <div class="codehilite"><pre><span class="n">CompositeComponentType</span> <span class="n">type</span> <span class="o">=</span> <span class="k">new</span> <span class="n">CompositeComponentType</span><span class="o">()</span>
        <span class="o">.</span><span class="na">setBundleContext</span><span class="o">(</span><span class="n">context</span><span class="o">)</span>
        <span class="o">.</span><span class="na">setComponentTypeName</span><span class="o">(</span><span class="s">&quot;compExport&quot;</span><span class="o">)</span>
@@ -505,7 +516,7 @@ You can also set the the managed service
                 may be trademarks or registered trademarks of their respective owners.
                 </div>
                 <div class="timestamp span3 offset2">
-                Rev. 1530195 by guillaume on Tue, 8 Oct 2013 09:12:32 +0000
+                Rev. 1700393 by cziegeler on Tue, 1 Sep 2015 06:04:06 +0000
                 </div>
             </div>
         </footer>



Mime
View raw message