You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@felix.apache.org by bu...@apache.org on 2015/09/01 08:05:20 UTC
svn commit: r963800 [9/16] - in /websites/staging/felix/trunk/content: ./
documentation/ documentation/community/ documentation/development/
documentation/faqs/ documentation/subprojects/
documentation/subprojects/apache-felix-commons/ documentation/su...
Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/ipojo-advanced-topics/using-ipojo-introspection-api.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/ipojo-advanced-topics/using-ipojo-introspection-api.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/ipojo-advanced-topics/using-ipojo-introspection-api.html Tue Sep 1 06:05:17 2015
@@ -171,7 +171,18 @@
<div class="container">
<div class="content">
- <h1 id="introspecting-instances">Introspecting instances</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="introspecting-instances">Introspecting instances<a class="headerlink" href="#introspecting-instances" title="Permanent link">¶</a></h1>
<p><em>iPOJO provides mechanisms to introspect and reconfigure instances. Those features are available from the instance description. Currently, only the reconfiguration of primitive instances is supported.</em></p>
<div class="toc">
<ul>
@@ -185,7 +196,7 @@
</li>
</ul>
</div>
-<h2 id="getting-instance-descriptions">Getting instance descriptions</h2>
+<h2 id="getting-instance-descriptions">Getting instance descriptions<a class="headerlink" href="#getting-instance-descriptions" title="Permanent link">¶</a></h2>
<p>There is two way to get the instance description:
<em> By using the <code>architecture</code> service exposed by an instance providing introspection support.
</em> By calling the <code>getInstanceDescription()</code> method on a ComponentInstance object (that you create thanks to a Factory)</p>
@@ -197,7 +208,7 @@
</pre></div>
-<h2 id="introspecting-primitive-instances">Introspecting primitive instances</h2>
+<h2 id="introspecting-primitive-instances">Introspecting primitive instances<a class="headerlink" href="#introspecting-primitive-instances" title="Permanent link">¶</a></h2>
<p>Once you get the object, cast it in (be sure that it is really a primitive instance).
Then, you have access to every primitive instance aspects:</p>
<ul>
@@ -265,7 +276,7 @@ Then, you have access to every primitive
</pre></div>
-<h2 id="manipulating-dependencies">Manipulating dependencies</h2>
+<h2 id="manipulating-dependencies">Manipulating dependencies<a class="headerlink" href="#manipulating-dependencies" title="Permanent link">¶</a></h2>
<p>You can get service dependencies from the <code>PrimitiveInstanceDescription</code>. Once you get the dependency (<code>DependencyDescription</code> object that you want to manipulate you can call one of those method on it:</p>
<div class="codehilite"><pre><span class="kd">public</span> <span class="kt">boolean</span> <span class="nf">isMultiple</span><span class="o">()</span> <span class="o">{</span> <span class="o">...</span> <span class="o">}</span>
@@ -347,7 +358,7 @@ Then, you have access to every primitive
<p>These methods allows getting the dependency state as well as reconfiguring the dependency by setting a new filter... </p>
<p>There is a slightly difference between the <code>getServiceReference(s)</code> methods and the <code>getUsedServices</code> method. The first ones returns the list of matching provider. The second one returns the list of currently used providers. </p>
-<h2 id="manipulating-provided-services">Manipulating provided services</h2>
+<h2 id="manipulating-provided-services">Manipulating provided services<a class="headerlink" href="#manipulating-provided-services" title="Permanent link">¶</a></h2>
<p>You also can manipulate provided services . </p>
<div class="codehilite"><pre><span class="cm">/**</span>
<span class="cm"> * Gets the list of provided service specifications.</span>
@@ -400,7 +411,7 @@ Then, you have access to every primitive
<p>Thanks to these method, you can get service objects, get the registered services, and manipulate service properties.</p>
-<h2 id="manipulating-configuration-properties">Manipulating configuration properties</h2>
+<h2 id="manipulating-configuration-properties">Manipulating configuration properties<a class="headerlink" href="#manipulating-configuration-properties" title="Permanent link">¶</a></h2>
<p>The last think that you can do from the <code>PrimitiveInstanceDescription</code> is to get configuration properties (<code>PropertyDescription</code>). </p>
<div class="codehilite"><pre><span class="cm">/**</span>
<span class="cm"> * Gets the current property name.</span>
@@ -446,7 +457,7 @@ Then, you have access to every primitive
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-userguide/ipojo-advanced-topics/using-stereotypes.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/ipojo-advanced-topics/using-stereotypes.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/ipojo-advanced-topics/using-stereotypes.html Tue Sep 1 06:05:17 2015
@@ -171,7 +171,18 @@
<div class="container">
<div class="content">
- <h1 id="stereotypes">Stereotypes</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="stereotypes">Stereotypes<a class="headerlink" href="#stereotypes" title="Permanent link">¶</a></h1>
<p><em>Stereotypes are user-defined marker annotations allowing to group other annotations together. iPOJO recognize these annotations and act as if all the grouped annotations were directly decorating the stereotyped annotation support.</em></p>
<div class="toc">
<ul>
@@ -191,7 +202,7 @@
</li>
</ul>
</div>
-<h2 id="example">Example</h2>
+<h2 id="example">Example<a class="headerlink" href="#example" title="Permanent link">¶</a></h2>
<p>The <code>@AutoComponent</code> is a stereotyped annotation (notice the <code>@Stereotype</code>) that will act as a 'container' for <code>@Component</code> and <code>@Instantiate</code>.</p>
<div class="codehilite"><pre><span class="nd">@Component</span>
<span class="nd">@Instantiate</span>
@@ -209,11 +220,11 @@
</pre></div>
-<h2 id="when-using-a-stereotype">When using a stereotype ?</h2>
+<h2 id="when-using-a-stereotype">When using a stereotype ?<a class="headerlink" href="#when-using-a-stereotype" title="Permanent link">¶</a></h2>
<p>Stereotypes are useful when writing extension of the iPOJO programming model. Sometimes, to keep things simple for the user, its necessary to hide some parts of iPOJO.</p>
<p>For example, a new programming model could mandates to have one-to-one factory/instance relationship. With iPOJO's programming model, writing <code>@Component</code> and <code>@Instantiate</code> (if using annotation) is required, this may be error prone when writing the new components: the developer could miss one annotation or the other.</p>
<p>Another example is to simplify annotation declaration when an annotation pattern appears (the same annotations group on many places of the code). Typically, introducing a stereotype defines a 'kind' that can be reused (code factorisation).</p>
-<h1 id="defining-a-stereotype">Defining a Stereotype</h1>
+<h1 id="defining-a-stereotype">Defining a Stereotype<a class="headerlink" href="#defining-a-stereotype" title="Permanent link">¶</a></h1>
<p>Stereotyped annotations, unlike custom handler annotations, do not need to be in a package containing either <code>ipojo</code> or <code>handler</code>. They just need to be annotated with <code>@Stereotype</code> (since iPOJO annotations 1.10.1) and have a class level rentention policy (the default when <code>@Retention</code> is missing). Any <code>@Target</code> can be specified (<code>TYPE</code>, <code>METHOD</code>, <code>FIELD</code>, <code>CONSTRUCTOR</code> and <code>ANNOTATION_TYPE</code> are supported), dependeding on the stereotype's semantic.</p>
<p>A stereotyped annotation can support all of the regular iPOJO's annotations plus all other externally supported types (custom handler, manipulator binding extensions, ...).</p>
<div class="codehilite"><pre><span class="kn">import</span> <span class="nn">com.acme.app.ipojo.Custom</span><span class="o">;</span> <span class="c1">// Import a custom handler annotation</span>
@@ -242,17 +253,17 @@
<p>The artifact containing the stereotyped annotation *does not need* to be a bundle and it does not need to be manipulated.</p>
</div>
-<h1 id="using-the-new-stereotype">Using the new stereotype</h1>
+<h1 id="using-the-new-stereotype">Using the new stereotype<a class="headerlink" href="#using-the-new-stereotype" title="Permanent link">¶</a></h1>
<p>Using a stereotyped annotation does not differ from using any annotation: it has decorate some type, method, field, ...</p>
-<h2 id="manipulation">Manipulation</h2>
+<h2 id="manipulation">Manipulation<a class="headerlink" href="#manipulation" title="Permanent link">¶</a></h2>
<p>Stereotype support needs iPOJO manipulator 1.10.1 (at least).</p>
<p>During the manipulation, the system search for all annotation definitions to find if they are @Stereotype annotated or not.</p>
<p>If the stereotyped annotation is directly in the manipulated module, no problems: any front-end will work as expected.</p>
<p>If not, the different manipulator's front-end have variable support for the stereotype feature.</p>
-<h3 id="with-bnd-ipojo-plugin">With bnd-ipojo-plugin</h3>
+<h3 id="with-bnd-ipojo-plugin">With bnd-ipojo-plugin<a class="headerlink" href="#with-bnd-ipojo-plugin" title="Permanent link">¶</a></h3>
<p>The more advanced support for stereotypes.</p>
<p>The plugin inspect <em>maven project's dependencies</em> provided to Bnd as its classpath to find stereotyped annotations definition.</p>
-<h3 id="with-others">With others</h3>
+<h3 id="with-others">With others<a class="headerlink" href="#with-others" title="Permanent link">¶</a></h3>
<p>No dependencies are analyzed at the moment.</p>
</div>
</div>
@@ -268,7 +279,7 @@
may be trademarks or registered trademarks of their respective owners.
</div>
<div class="timestamp span3 offset2">
- Rev. 1489150 by guillaume on Mon, 3 Jun 2013 20:20:03 +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/ipojo-faq.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/ipojo-faq.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/ipojo-faq.html Tue Sep 1 06:05:17 2015
@@ -171,7 +171,18 @@
<div class="container">
<div class="content">
- <h1 id="apache-felix-ipojo-faq">Apache Felix iPOJO FAQ</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-faq">Apache Felix iPOJO FAQ<a class="headerlink" href="#apache-felix-ipojo-faq" title="Permanent link">¶</a></h1>
<div class="toc">
<ul>
<li><a href="#apache-felix-ipojo-faq">Apache Felix iPOJO FAQ</a><ul>
@@ -193,7 +204,7 @@
</li>
</ul>
</div>
-<h2 id="injecting-the-bundle-context-in-a-pojo">Injecting the bundle context in a POJO</h2>
+<h2 id="injecting-the-bundle-context-in-a-pojo">Injecting the bundle context in a POJO<a class="headerlink" href="#injecting-the-bundle-context-in-a-pojo" title="Permanent link">¶</a></h2>
<p>It is sometimes useful to inject the bundle context in your POJO. Then, your POJO is able to deal with the OSGi environment as <em>regular</em> OSGi applications. It is possible to a POJO to get its <code>BundleContext</code>. A POJO can receive its bundle context as an argument of its constructor. The next code snippet shows an example:</p>
<div class="codehilite"><pre><span class="kd">public</span> <span class="kd">class</span> <span class="nc">ASimplePOJO</span><span class="o">{</span>
<span class="kd">private</span> <span class="n">BundleContext</span> <span class="n">context</span><span class="o">;</span>
@@ -212,10 +223,10 @@
<li>discover, track and use services</li>
</ul>
<p>However, all these interactions are no more managed by the iPOJO container. So, be careful to manage the dynamism, synchronization, listeners...</p>
-<h2 id="accessing-services-inside-inner-and-anonymous-classes">Accessing services inside inner and anonymous classes</h2>
+<h2 id="accessing-services-inside-inner-and-anonymous-classes">Accessing services inside inner and anonymous classes<a class="headerlink" href="#accessing-services-inside-inner-and-anonymous-classes" title="Permanent link">¶</a></h2>
<p>An inner class is a class defined inside another class. This mechanism is useful in order to avoid creating a bunch of small files. So, it is common when creating threads, Swing listeners ... Generally speaking, inner classes are regular classes treated as separate classes. However this is an oversimplification. Some of the information about an inner class is not in its class file. See section 4.7.5 for further details on [http://java.sun.com/docs/books/jvms/second_edition/html/ClassFile.doc.html]</p>
<p>An inner class can access fields of its outer class. Since the iPOJO 1.0.0 version, fields managed by iPOJO, such as a service dependencies and properties, are also available from the inner class. Indeed, iPOJO manipulation also manipulates inner and nested classes, and accesses to outer class fields are correctly managed.</p>
-<h2 id="using-a-different-version-of-the-manipulator-during-the-manipulation">Using a different version of the manipulator during the manipulation</h2>
+<h2 id="using-a-different-version-of-the-manipulator-during-the-manipulation">Using a different version of the manipulator during the manipulation<a class="headerlink" href="#using-a-different-version-of-the-manipulator-during-the-manipulation" title="Permanent link">¶</a></h2>
<p>You can configure the version of the manipulator that you want to use when you're using the maven-ipojo-plugin or the iPOJO ant task. This allows to benefit latest improvements.</p>
<p>For Maven, Just declare a dependency on the manipulator that you want to use in the maven-ipojo-plugin plugin section:</p>
<div class="codehilite"><pre><span class="nt"><plugin></span>
@@ -246,7 +257,7 @@
</pre></div>
-<h2 id="callbacks-order">Callbacks order.</h2>
+<h2 id="callbacks-order">Callbacks order.<a class="headerlink" href="#callbacks-order" title="Permanent link">¶</a></h2>
<p>A lot of handlers define callbacks to notify the implementation class. The 'core' callbacks are called in the following order:</p>
<div class="codehilite"><pre><span class="nd">@Component</span>
<span class="nd">@Provides</span>
@@ -307,7 +318,7 @@
</pre></div>
-<h2 id="disabling-proxies-in-ipojo-16">Disabling proxies in iPOJO 1.6+</h2>
+<h2 id="disabling-proxies-in-ipojo-16">Disabling proxies in iPOJO 1.6+<a class="headerlink" href="#disabling-proxies-in-ipojo-16" title="Permanent link">¶</a></h2>
<p>iPOJO 1.6.0 has generalized the proxy usage. However this mechanism can be disabled.</p>
<p>To disable the proxies on the entire framework, just set the property <code>ipojo.proxy</code> to <code>disabled</code> (this set the default 'proxy' value). This property is either a system property (<code>-Dipojo.proxy=disabled</code> in the command line) or a framework property (given to the framework during its initialization).</p>
<p>You can also disable proxies for specific dependencies by using the <code>proxy</code> attribute:</p>
@@ -322,12 +333,12 @@
<p>The default value of the <code>proxy</code> attribute is the value of the <code>ipojo.proxy</code> property.</p>
-<h2 id="use-dynamic-proxies-instead-of-smart-proxies">Use dynamic proxies instead of smart proxies</h2>
+<h2 id="use-dynamic-proxies-instead-of-smart-proxies">Use dynamic proxies instead of smart proxies<a class="headerlink" href="#use-dynamic-proxies-instead-of-smart-proxies" title="Permanent link">¶</a></h2>
<p>Smart proxies are generated on the fly using bytecode generation. However this mechanism may not be always supported by the VM (like Dalvik (Android)). To disabled smart proxies (used by default) and use dynamic proxy instead, set the property <code>ipojo.proxy.type</code> to <code>dynamic-proxy</code>. This property is either a system property or a framework property.</p>
-<h2 id="can-i-use-ipojo-with-other-osgi-implementations">Can I use iPOJO with other OSGi implementations?</h2>
+<h2 id="can-i-use-ipojo-with-other-osgi-implementations">Can I use iPOJO with other OSGi implementations?<a class="headerlink" href="#can-i-use-ipojo-with-other-osgi-implementations" title="Permanent link">¶</a></h2>
<p>iPOJO relies on the OSGi R4.1 specification, so works on any compliant implementation. Moreover, iPOJO is weekly tested on Apache Felix, Eclipse Equinox and Knopflerfish..</p>
<p>For further information, refer to the <a href="/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-supportedosgi.html">supported OSGi implementations</a> page and on this [blog|http://ipojo-dark-side.blogspot.com/2008/11/lessons-learned-from-ipojo-testing.html] post.</p>
-<h2 id="detecting-optional-service-unavailability">Detecting optional service unavailability</h2>
+<h2 id="detecting-optional-service-unavailability">Detecting optional service unavailability<a class="headerlink" href="#detecting-optional-service-unavailability" title="Permanent link">¶</a></h2>
<p>Sometimes it is useful to check if an optional service dependency is fulfilled or not. In order to propose a pretty simple development model, iPOJO injects proxies by default which avoid such check (Because proxies hide such details). By disabling proxies, you can easily check to unavailability.</p>
<ul>
<li>
@@ -363,7 +374,7 @@ private LogService log;</p>
}</p>
</li>
</ul>
-<h2 id="setting-the-ipojo-log-level">Setting the iPOJO log level</h2>
+<h2 id="setting-the-ipojo-log-level">Setting the iPOJO log level<a class="headerlink" href="#setting-the-ipojo-log-level" title="Permanent link">¶</a></h2>
<p>By default, iPOJO logs only warning and error messages. There are two different methods to configure the log level. First, you can set the global log level by setting the <em>ipojo.log.level</em> system property. This replaces the default log level (warning). All iPOJO instances will be impacted. However, each bundle containing component types can specify a different log level. To set this level, add the <em>ipojo-log-level</em> header in your manifest. The possible values for these two properties are:</p>
<div class="codehilite"><pre><span class="o">*</span> <span class="n">info</span>
<span class="o">*</span> <span class="n">debug</span>
@@ -372,16 +383,16 @@ private LogService log;</p>
</pre></div>
-<h2 id="installing-ipojo-in-service-mix-kernel">Installing iPOJO in Service Mix Kernel</h2>
+<h2 id="installing-ipojo-in-service-mix-kernel">Installing iPOJO in Service Mix Kernel<a class="headerlink" href="#installing-ipojo-in-service-mix-kernel" title="Permanent link">¶</a></h2>
<p>You can use iPOJO in Service Mix Kernel. To deploy and start it, just execute the following command line in the ServiceMix Kernel Shell.</p>
<div class="codehilite"><pre>osgi install -s mvn:org.apache.felix/org.apache.felix.ipojo/1.2.0
</pre></div>
<p>The iPOJO bundle is downloaded from the central maven repository.</p>
-<h2 id="ipojo-and-file-install">iPOJO and File Install</h2>
+<h2 id="ipojo-and-file-install">iPOJO and File Install<a class="headerlink" href="#ipojo-and-file-install" title="Permanent link">¶</a></h2>
<p>Thanks to File install you can create, disposed and reconfigure instances from <em>cfg</em> files. You can also reconfiguring a creatged instance (configured to expose a <a href="http://felix.apache.org/site/configuration-handler.html#ConfigurationHandler-ExposingaManagedService">ManagedService</a>) with <em>cfg</em> files too. More information about this topic is available [here|http://ipojo-dark-side.blogspot.com/2009/04/ipojo-and-file-install-configuring.html].</p>
-<h2 id="ipojo-handler-start-level">iPOJO handler <em>start</em> level</h2>
+<h2 id="ipojo-handler-start-level">iPOJO handler <em>start</em> level<a class="headerlink" href="#ipojo-handler-start-level" title="Permanent link">¶</a></h2>
<p>iPOJO Handlers have a <em>start</em> level. This is <em>not</em> the <code>OSGi Start Level</code>. This level is used to determine in which order handler are configured, started and stopped. Handlers with a low level are configured and started before handlers with a high level. Moreover they are stopped after handlers with a high level. By default, handlers have no level. It means that they have the maximum level (<code>Integer.MAX</code>).</p>
<p>Here are the levels of core handlers:</p>
<ul>
@@ -403,7 +414,7 @@ private LogService log;</p>
iPOJO 1.3.0-SNAPSHOT sets the lifecycle callback handler level to 2. So, setter methods from instance properties are called before the validate method.
</div>
-<h2 id="why-does-my-bundle-import-unused-packages">Why does my bundle import unused packages?</h2>
+<h2 id="why-does-my-bundle-import-unused-packages">Why does my bundle import unused packages?<a class="headerlink" href="#why-does-my-bundle-import-unused-packages" title="Permanent link">¶</a></h2>
<p>If you check iPOJO bundle imported packages, you will see that some packages where added:</p>
<ul>
<li>org.apache.felix.ipojo;version= 1.2.0</li>
@@ -414,7 +425,7 @@ iPOJO 1.3.0-SNAPSHOT sets the lifecycle
<p>The <code>org.apache.felix.ipojo</code> package is the main iPOJO package. Manipulated class use it to get access to injected values. The <code>org.apache.felix.ipojo.architecture</code> package is used to expose <em>Architecture</em> service (allowing instance introspection). This service is exposed with the bundle context from the bundle declaring the component type.</p>
<p>The <code>org.osgi.service.cm</code> package is imported to publish <em>ManagedService</em> and <em>ManagedServiceFactory</em> with the bundle context from the bundle declaring the component type. So, if you look for services exposed by a bundle declaring component types, you will see <em>ManagedServiceFactory</em> services.
Finally, the <code>org.osgi.service.log</code> is imported because iPOJO delegates log to a log service (if available). This service is get from the bundle context from the bundle declaring the component type. So, to get this service, the package of the service interface is imported. Then, according to implementations, log services may get the bundle logging the message.</p>
-<h2 id="how-does-ipojo-compare-to-declarative-services-or-blueprint">How does iPOJO compare to Declarative Services or Blueprint?</h2>
+<h2 id="how-does-ipojo-compare-to-declarative-services-or-blueprint">How does iPOJO compare to Declarative Services or Blueprint?<a class="headerlink" href="#how-does-ipojo-compare-to-declarative-services-or-blueprint" title="Permanent link">¶</a></h2>
<p>The following table highlights some of the features of each system, it does not attempt to highlight every feature of each.</p>
<table class="table table-striped">
<thead>
@@ -615,7 +626,7 @@ Finally, the <code>org.osgi.service.log<
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-userguide/using-xml-schemas.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/using-xml-schemas.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/using-xml-schemas.html Tue Sep 1 06:05:17 2015
@@ -171,7 +171,18 @@
<div class="container">
<div class="content">
- <h1 id="using-xml-schemas">Using XML Schemas</h1>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="using-xml-schemas">Using XML Schemas<a class="headerlink" href="#using-xml-schemas" title="Permanent link">¶</a></h1>
<p><em>iPOJO provides XML schemas to check iPOJO descriptors (i.e. metadata.xml). Several schemas are provided in order to describe the core syntax, compositions and external handlers.</em></p>
<table class="table"><tbody>
<tr>
@@ -244,7 +255,7 @@ You can also use several schemas in the
<p>The only difference is contained in the 'schemaLocation' attribute, which contains several pairs. You also need to declare the namespace of the used external handler.</p>
<p>If you declare schemas, the iPOJO manipulator automatically checks the validity of the descriptor against the declared schemas. Moreover, if you use 'advanced' XML Editor supporting schemas, editing iPOJO descriptors should be eased with auto-completion features.</p>
-<h2 id="avoid-downloading-xml-schemas-during-the-build-process">Avoid downloading XML Schemas during the build process</h2>
+<h2 id="avoid-downloading-xml-schemas-during-the-build-process">Avoid downloading XML Schemas during the build process<a class="headerlink" href="#avoid-downloading-xml-schemas-during-the-build-process" title="Permanent link">¶</a></h2>
<p>The manipulator embeds the iPOJO XML Schemas to avoid using a network connection to download them during the validation process. Keep the same url, the manipulator will just resolve the URL differently to use embedded schemas. You can also skipped this shortcut thanks the the <code>ignoreEmbeddedSchemas</code> parameter (refer to the <a href="/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/ipojo-ant-task.html">Ant Task</a>) and to the <a href="/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/ipojo-maven-plug-in.html">Maven Plugin</a> for further information about configuration).</p>
</div>
</div>
@@ -260,7 +271,7 @@ You can also use several schemas in the
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-why-choose-ipojo.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-why-choose-ipojo.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-why-choose-ipojo.html Tue Sep 1 06:05:17 2015
@@ -171,10 +171,21 @@
<div class="container">
<div class="content">
- <h1 id="why-choose-ipojo">Why choose iPOJO?</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="why-choose-ipojo">Why choose iPOJO?<a class="headerlink" href="#why-choose-ipojo" title="Permanent link">¶</a></h1>
<p><em>The OSGi Service Platform provides an excellent foundation for building dynamically extensible Java-based applications. However, such power and flexibility does not come without cost. In addition to new APIs and packaging formats, OSGi developers must shift their thinking to be able to design highly dynamic applications. Early efforts, such as the Service Binder and Service Tracker, attempted to alleviate some of these issues, as well as more recent efforts, such as Declarative Services and Spring Dynamic Modules. iPOJO is another such effort in this area. It is a service-oriented component model created </em>specifically<em> for the OSGi Service Platform.</em></p>
<p><em>The purpose behind iPOJO is twofold. The first goal is to simplify OSGi development to the bare necessities. This means that providing services, using services, and dealing with dynamism should require as little effort as possible from the developer. The second goal is to push beyond support for basic OSGi mechanisms and try to more seamlessly incorporate advanced features, including component configuration, synchronization, and composition. This page summaries the key point of iPOJO.</em></p>
-<h2 id="simplicity">Simplicity</h2>
+<h2 id="simplicity">Simplicity<a class="headerlink" href="#simplicity" title="Permanent link">¶</a></h2>
<p>Trying to create an OSGi-based application with services is challenging. The OSGi API is complex and a lot of knowledge about internal mechanisms has to be known to avoid synchronization issues. iPOJO provides a very simple development model; let's have a look:</p>
<p>To provide a service:</p>
<div class="codehilite"><pre><span class="nd">@Component</span>
@@ -197,13 +208,13 @@
<p>Isn't that easy? Providing and requiring OSGi services have never been so simple.</p>
-<h2 id="power">Power</h2>
+<h2 id="power">Power<a class="headerlink" href="#power" title="Permanent link">¶</a></h2>
<p>Supporting OSGi services is not the only feature of iPOJO. iPOJO provides many other features that to simplify developing sophisticated applications. For example, iPOJO supports configuring components with Configuration Admin, sending/receiving events with the Event Admin, remote configuration with JMX, and more.</p>
-<h2 id="flexibility">Flexibility</h2>
+<h2 id="flexibility">Flexibility<a class="headerlink" href="#flexibility" title="Permanent link">¶</a></h2>
<p>Is iPOJO missing a feature you need? No problem. iPOJO provides an extensibility mechanism that allows you to mange other (custom) requirements. You can easily adapt iPOJO for your own needs. Creating an extension does not require modifications to the core, you only need to implement a custom <em>handler</em> that will be plugged on your instance. Your handlers can also use any of the other iPOJO features.</p>
-<h2 id="portability">Portability</h2>
+<h2 id="portability">Portability<a class="headerlink" href="#portability" title="Permanent link">¶</a></h2>
<p>iPOJO works on any R4.1 OSGi implementation. It also works on many Java virtual machines such as Oracle JRockit, JamVM, Dalvik (Android), and Mika. iPOJO only requires a <em>J2ME Foundation 1.1</em> virtual machine. So, iPOJO can be embedded inside mobile phone applications or inside your washing machine.</p>
-<h2 id="performance">Performance</h2>
+<h2 id="performance">Performance<a class="headerlink" href="#performance" title="Permanent link">¶</a></h2>
<p>Being powerful is great, but what about footprint and performances? iPOJO is small and was designed to stay small. The core size of iPOJO is approximately <em>205k</em> (compared to 816k for Guice-Peaberry and 2112k for the minimal Spring-DM configuration). In addition to the core, you only deploy the features you require. For example, if you need proxy injection, just deploy the temporal dependency bundle (less than 70Kb).</p>
<p>The run-time overhead of iPOJO is also small. On the <a href="http://code.google.com/p/peaberry/wiki/Benchmarks">Peaberry benchmark</a>, iPOJO has very good performance:</p>
<div class="codehilite"><pre>Guice-Peaberry: 276.00 ns/call
@@ -215,11 +226,11 @@ iPOJO Temporal Dependency w/ proxy: 173
<p>For French readers, you can find additional benchmarks in chapter 10 of <a href="http://clement.plop-plop.net/thesis/These%20-%20FINAL.pdf">iPOJO - A flexible service-oriented component model for dynamic systems</a></p>
-<h2 id="development-support">Development support</h2>
+<h2 id="development-support">Development support<a class="headerlink" href="#development-support" title="Permanent link">¶</a></h2>
<p>Developing OSGi applications can quickly become a nightmare, when things are working as expected. iPOJO helps you debug your application (and it often happen). For starters, you can debug iPOJO components as normal OSGi applications (stack traces and line number are not modified). But thanks to iPOJO's introspection mechanisms, you can also know the structure of your application (which instance uses which service...), so you easily understand why a service dependency is not fulfilled, the value of properties, etc.</p>
-<h2 id="design-support">Design support</h2>
+<h2 id="design-support">Design support<a class="headerlink" href="#design-support" title="Permanent link">¶</a></h2>
<p>iPOJO also provides an architecture description language to design applications in a flexible and hierarchic manner. Designed applications are expressed in terms of services and are natively dynamic, meaning they support implementation evolution and substitution. Moreover, iPOJO supports service isolation to get your own private service.</p>
-<h2 id="conclusion">Conclusion</h2>
+<h2 id="conclusion">Conclusion<a class="headerlink" href="#conclusion" title="Permanent link">¶</a></h2>
<p><a href="/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-gettingstarted/ipojo-in-10-minutes.html">Give it a try!</a>.</p>
<p>For any questions or feedback, send an email on the <a href="mailto:users@felix.apache.org">users@felix.apache.org</a> mailing list (send a mail to <a href="mailto:users-subscribe@felix.apache.org">users-subscribe@felix.apache.org</a> to subscribe).</p>
</div>
@@ -236,7 +247,7 @@ iPOJO Temporal Dependency w/ proxy: 173
may be trademarks or registered trademarks of their respective owners.
</div>
<div class="timestamp span3 offset2">
- Rev. 1443051 by clement on Wed, 6 Feb 2013 16:33:33 +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/articles-and-presentations.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/articles-and-presentations.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/articles-and-presentations.html Tue Sep 1 06:05:17 2015
@@ -171,17 +171,28 @@
<div class="container">
<div class="content">
- <h1 id="presentations">Presentations</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="presentations">Presentations<a class="headerlink" href="#presentations" title="Permanent link">¶</a></h1>
<ul>
<li>"iPOJO : This Simple Life", OSGi Community Event 2008, Berlin, Germany. <a href="http://felix.apache.org/site/presentations.data/ipojo-berlin-20080611.pdf">Download</a></li>
<li>"iPOJO : A flexible service-oriented component model for dynamic systems", PHD Defense, December 2008, Grenoble, France.</li>
</ul>
-<h1 id="articles-on-ipojo-core-features">Articles on iPOJO Core features</h1>
+<h1 id="articles-on-ipojo-core-features">Articles on iPOJO Core features<a class="headerlink" href="#articles-on-ipojo-core-features" title="Permanent link">¶</a></h1>
<ul>
<li>Clement Escoffier, Richard S. Hall and Philippe Lalanda, iPOJO An extensible service-oriented component framework IEEE Service Computing Conference 2007 (SCC 2007) July 2007, Salt Lake City, Utah (USA)</li>
<li>Clement Escoffier and Richard S. Hall, Dynamically Adaptable Applications with iPOJO Service Components (<a href="http://www-adele.imag.fr/Les.Publications/intConferences/SC2007Esc.pdf">pdf</a>) 6th International Symposium on Software Composition (SC 2007) March 2007, Braga, Portugal</li>
</ul>
-<h1 id="articles-using-ipojo">Articles using iPOJO</h1>
+<h1 id="articles-using-ipojo">Articles using iPOJO<a class="headerlink" href="#articles-using-ipojo" title="Permanent link">¶</a></h1>
<p>Check the list of academic papers using iPOJO on <a href="http://scholar.google.com/scholar?hl=en&q=ipojo&btnG=&as_sdt=1%2C5&as_sdtp=">Google scholar</a></p>
</div>
</div>
@@ -197,7 +208,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/developing-camel-mediators-with-ipojo.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/developing-camel-mediators-with-ipojo.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/developing-camel-mediators-with-ipojo.html Tue Sep 1 06:05:17 2015
@@ -171,16 +171,27 @@
<div class="container">
<div class="content">
- <h1 id="developing-camel-mediators-with-ipojo">Developing Camel mediators with iPOJO</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="developing-camel-mediators-with-ipojo">Developing Camel mediators with iPOJO<a class="headerlink" href="#developing-camel-mediators-with-ipojo" title="Permanent link">¶</a></h1>
<p><em>The <a href="http://camel.apache.org/tutorial-osgi-camel-part1.html">Camel OSGi tutorial </a> provides a very simple and neat overview of Camel. This article mentions the usage of iPOJO to implement the mediator. This document provides this implementation.</em></p>
-<h2 id="step-1-initial-project-setup">Step 1 : Initial project setup</h2>
+<h2 id="step-1-initial-project-setup">Step 1 : Initial project setup<a class="headerlink" href="#step-1-initial-project-setup" title="Permanent link">¶</a></h2>
<p>Instead of using the 'spring-osgi-bundle-archetype' maven archetype, we will use the iPOJO one to create the iPOJO bundle.
To create the simple iPOJO service project, execute the following command in your Unix/Dos console.</p>
<div class="codehilite"><pre>mvn archetype:create -DarchetypeGroupId<span class="o">=</span>org.apache.felix -DarchetypeArtifactId<span class="o">=</span>maven-ipojo-plugin -DarchetypeVersion<span class="o">=</span>1.0.0 -DgroupId<span class="o">=</span>demo -DartifactId<span class="o">=</span>demo.service-ipojo-bundle -Dversion<span class="o">=</span>0.1
</pre></div>
-<h2 id="step-2-develop-the-interface">Step 2 : Develop the interface</h2>
+<h2 id="step-2-develop-the-interface">Step 2 : Develop the interface<a class="headerlink" href="#step-2-develop-the-interface" title="Permanent link">¶</a></h2>
<p>So now, it is time to create the interface that we will use in the project. Create a new folder "service" in <code>src/main/java/demo</code> tree. Add the interface <code>TransformService.java</code> and copy paste the code below:</p>
<div class="codehilite"><pre><span class="kn">package</span> <span class="n">demo</span><span class="o">.</span><span class="na">service</span><span class="o">;</span>
<span class="kd">public</span> <span class="kd">interface</span> <span class="nc">TransformService</span> <span class="o">{</span>
@@ -189,7 +200,7 @@ To create the simple iPOJO service proje
</pre></div>
-<h2 id="step-3-create-the-class-implementing-the-interface">Step 3 : Create the class implementing the interface</h2>
+<h2 id="step-3-create-the-class-implementing-the-interface">Step 3 : Create the class implementing the interface<a class="headerlink" href="#step-3-create-the-class-implementing-the-interface" title="Permanent link">¶</a></h2>
<p>Next, we will create the class <code>TransformServiceImpl</code> implementing the interface <code>TransformService</code>. Create the class <code>TransformServiceImpl.java</code> in the folder <code>src/main/java/demo/service/</code></p>
<div class="codehilite"><pre><span class="kn">package</span> <span class="n">demo</span><span class="o">.</span><span class="na">service</span><span class="o">;</span>
@@ -231,7 +242,7 @@ To create the simple iPOJO service proje
</pre></div>
-<h2 id="step-4-create-the-ipojo-configuration-files">Step 4 : Create the iPOJO configuration files</h2>
+<h2 id="step-4-create-the-ipojo-configuration-files">Step 4 : Create the iPOJO configuration files<a class="headerlink" href="#step-4-create-the-ipojo-configuration-files" title="Permanent link">¶</a></h2>
<p>The next step concerns the creation of the iPOJO configuration file who will allow the registration of the <code>TranformService</code> as an OSGi service.
Create or edit the file <code>metadata.xml</code> in the folder <code>src/main/resources/</code></p>
<div class="codehilite"><pre><span class="cp"><?xml version="1.0" encoding="UTF-8"?></span>
@@ -244,7 +255,7 @@ Create or edit the file <code>metadata.x
</pre></div>
-<h2 id="step-5-generate-the-bundle">Step 5 : Generate the bundle</h2>
+<h2 id="step-5-generate-the-bundle">Step 5 : Generate the bundle<a class="headerlink" href="#step-5-generate-the-bundle" title="Permanent link">¶</a></h2>
<p>Before generating the bundle, we need to edit the file to describe our bundle.</p>
<div class="codehilite"><pre><span class="nt"><project></span>
<span class="nt"><modelVersion></span>4.0.0<span class="nt"></modelVersion></span>
@@ -317,7 +328,7 @@ Create or edit the file <code>metadata.x
</pre></div>
-<h2 id="step-6-7-create-the-camel-context-file-and-the-bundle">Step 6 & 7: Create the Camel context file and the bundle</h2>
+<h2 id="step-6-7-create-the-camel-context-file-and-the-bundle">Step 6 & 7: Create the Camel context file and the bundle<a class="headerlink" href="#step-6-7-create-the-camel-context-file-and-the-bundle" title="Permanent link">¶</a></h2>
<p>These steps are exactly the same as into the OSGi Camel Tutorial. So refer to the step 6 and 7 of the <a href="http://camel.apache.org/tutorial-osgi-camel-part1.html">article</a>. That's it. Deploy and enjoy.</p>
</div>
</div>
@@ -333,7 +344,7 @@ Create or edit the file <code>metadata.x
may be trademarks or registered trademarks of their respective owners.
</div>
<div class="timestamp span3 offset2">
- Rev. 1475720 by clement on Thu, 25 Apr 2013 12:13:11 +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/download.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/download.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/download.html Tue Sep 1 06:05:17 2015
@@ -171,10 +171,21 @@
<div class="container">
<div class="content">
- <h1 id="download-ipojo">Download iPOJO</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="download-ipojo">Download iPOJO<a class="headerlink" href="#download-ipojo" title="Permanent link">¶</a></h1>
<p><em>The actual iPOJO version is the </em>1.8.x<em>. This page contains links to download iPOJO binaries and sources of the latest version.</em></p>
-<h2 id="binaries-files">Binaries files</h2>
-<table>
+<h2 id="binaries-files">Binaries files<a class="headerlink" href="#binaries-files" title="Permanent link">¶</a></h2>
+<table class="table">
<thead>
<tr>
<th>Bundle or Jar file</th>
@@ -223,7 +234,7 @@
</tbody>
</table>
<p>| Maven Plug-in | 1.8.6 | Automatic download from the Maven repository | The iPOJO Maven plug-in allow creating iPOJO bundle with Maven. Using this plug-in requires that you configure your POM file correctly as explained <a href="/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/ipojo-maven-plug-in.html">here</a>. This [tutorial |iPOJO Hello Word (Maven-Based) tutorial]demonstrates how to use this plug-in to build iPOJO bundle (both for individual project and multi-module project). |</p>
-<table>
+<table class="table">
<thead>
<tr>
<th>Extender Pattern Handler</th>
@@ -257,7 +268,7 @@
</tr>
</tbody>
</table>
-<h2 id="sources">Sources</h2>
+<h2 id="sources">Sources<a class="headerlink" href="#sources" title="Permanent link">¶</a></h2>
<p>iPOJO Sources are available on the Apache Felix Project source trunk. To download iPOJO sources, use the following command:
{code:html}
svn checkout https://svn.apache.org/repos/asf/felix/trunk/ipojo</p>
@@ -276,7 +287,7 @@ mvn clean install -Pexamples</p>
</pre></div>
-<h2 id="executing-ipojo-tests">Executing iPOJO tests</h2>
+<h2 id="executing-ipojo-tests">Executing iPOJO tests<a class="headerlink" href="#executing-ipojo-tests" title="Permanent link">¶</a></h2>
<p>iPOJO Tests use the <code>junit4osgi</code> framework and <code>pax exam</code>. To execute tests, just compile them (with the <code>mvn clean install</code> from the <code>tests</code> directory) and then execute the integration tests by executing the <code>mvn clean integration-test</code> command from the <code>tests/integration-tests</code> folder.</p>
</div>
</div>
@@ -292,7 +303,7 @@ mvn clean install -Pexamples</p>
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/ipojo-reference-card.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/ipojo-reference-card.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/ipojo-reference-card.html Tue Sep 1 06:05:17 2015
@@ -171,7 +171,18 @@
<div class="container">
<div class="content">
- <h1 id="declaring-component-types">Declaring component types</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="declaring-component-types">Declaring component types<a class="headerlink" href="#declaring-component-types" title="Permanent link">¶</a></h1>
<p>XML:</p>
<div class="codehilite"><pre><span class="nt"><component</span>
<span class="na">classname=</span><span class="s">"my.Implementation"</span>
@@ -216,7 +227,7 @@
<ul>
<li><a href="/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/ipojo-advanced-topics/how-to-use-ipojo-factories.html">How-to use iPOJO factories</a></li>
</ul>
-<h1 id="creating-component-instances">Creating component instances</h1>
+<h1 id="creating-component-instances">Creating component instances<a class="headerlink" href="#creating-component-instances" title="Permanent link">¶</a></h1>
<p>XML:</p>
<div class="codehilite"><pre><span class="nt"><instance</span> <span class="na">component=</span><span class="s">"my-type"</span><span class="nt">/></span>
<span class="nt"><instance</span> <span class="na">component=</span><span class="s">"my.Implementation"</span><span class="nt">/></span>
@@ -265,7 +276,7 @@
<li>Instances can contains a configuration given under the <code>key-value</code> form. Properties can also by complex type.</li>
<li>How-to use iPOJO factories</li>
</ul>
-<h1 id="providing-services">Providing services</h1>
+<h1 id="providing-services">Providing services<a class="headerlink" href="#providing-services" title="Permanent link">¶</a></h1>
<p>XML:</p>
<div class="codehilite"><pre><span class="nt"><component</span> <span class="na">classname=</span><span class="s">"my.service.implementation"</span> <span class="na">name=</span><span class="s">"my-service-impl"</span><span class="nt">></span>
<span class="nt"><provides/></span>
@@ -315,7 +326,7 @@
<ul>
<li><a href="/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/providing-osgi-services.html">Providing OSGi services</a></li>
</ul>
-<h1 id="publishing-service-properties">Publishing service properties</h1>
+<h1 id="publishing-service-properties">Publishing service properties<a class="headerlink" href="#publishing-service-properties" title="Permanent link">¶</a></h1>
<p>XML:</p>
<div class="codehilite"><pre><span class="nt"><component</span> <span class="na">classname=</span><span class="s">"my.service.implementation"</span> <span class="na">name=</span><span class="s">"my-service-impl"</span><span class="nt">></span>
<span class="nt"><provides></span>
@@ -395,7 +406,7 @@
<ul>
<li><a href="/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/providing-osgi-services.html">Providing OSGi services</a></li>
</ul>
-<h1 id="using-services-with-field-injection">Using services with field injection</h1>
+<h1 id="using-services-with-field-injection">Using services with field injection<a class="headerlink" href="#using-services-with-field-injection" title="Permanent link">¶</a></h1>
<p>XML:</p>
<div class="codehilite"><pre><span class="nt"><component</span> <span class="na">classname=</span><span class="s">"my.consumer.Implementation"</span><span class="nt">></span>
<span class="nt"><requires</span> <span class="na">field=</span><span class="s">"fs"</span> <span class="nt">/></span>
@@ -501,7 +512,7 @@
<ul>
<li><a href="/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/service-requirement-handler.html">Service Requirement Handler</a></li>
</ul>
-<h1 id="using-services-with-method-injection">Using services with method injection</h1>
+<h1 id="using-services-with-method-injection">Using services with method injection<a class="headerlink" href="#using-services-with-method-injection" title="Permanent link">¶</a></h1>
<p>XML:</p>
<div class="codehilite"><pre><span class="nt"><component</span> <span class="na">classname=</span><span class="s">"my.consumer.Implementation"</span><span class="nt">></span>
<span class="nt"><requires></span>
@@ -551,7 +562,7 @@
| nullable | no | true | enables/disables nullable object injection for optional dependencies |
| default-implementation // default implementation for annotations | no | | specifies the default-implementation for optional dependencies |
| comparator | no | | specifies the comparator class used to sort service providers |</p>
-<table>
+<table class="table">
<thead>
<tr>
<th>Sub-Element name</th>
@@ -568,13 +579,13 @@
<td></td>
</tr>
<tr>
-<td>{center}</td>
+<td center="center"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
-<td>{div}</td>
+<td div="div"></td>
<td></td>
<td></td>
<td></td>
@@ -587,7 +598,7 @@
</tr>
</tbody>
</table>
-<h1 id="configuring-service-dependencies-in-the-instance-configuration">Configuring service dependencies in the instance configuration</h1>
+<h1 id="configuring-service-dependencies-in-the-instance-configuration">Configuring service dependencies in the instance configuration<a class="headerlink" href="#configuring-service-dependencies-in-the-instance-configuration" title="Permanent link">¶</a></h1>
<p>h2. Configuring the <code>from</code> attribute
* Thanks to the <code>requires.from</code> property, it is possible to override the <code>from</code> attribute value.</p>
<p>{code:xml|From attribute configuration}
@@ -628,8 +639,8 @@
</pre></div>
-<h1 id="reacting-to-lifecycle-state-changes">Reacting to lifecycle state changes</h1>
-<h2 id="immediate-components">Immediate components</h2>
+<h1 id="reacting-to-lifecycle-state-changes">Reacting to lifecycle state changes<a class="headerlink" href="#reacting-to-lifecycle-state-changes" title="Permanent link">¶</a></h1>
+<h2 id="immediate-components">Immediate components<a class="headerlink" href="#immediate-components" title="Permanent link">¶</a></h2>
<ul>
<li>A POJO object (implementation object) is created as soons as the instance becomes valid</li>
<li>
@@ -654,7 +665,7 @@ public class Implementation implements F
{center}
{div}
* <a href="/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/lifecycle-callback-handler.html">Lifecycle Callback Handler</a></p>
-<h2 id="lifecycle-callbacks">Lifecycle callbacks</h2>
+<h2 id="lifecycle-callbacks">Lifecycle callbacks<a class="headerlink" href="#lifecycle-callbacks" title="Permanent link">¶</a></h2>
<div class="codehilite"><pre>
</pre></div>
@@ -683,7 +694,7 @@ public class Implementation implements F
<ul>
<li><a href="/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/lifecycle-callback-handler.html">Lifecycle Callback Handler</a></li>
</ul>
-<h1 id="declaring-properties">Declaring properties</h1>
+<h1 id="declaring-properties">Declaring properties<a class="headerlink" href="#declaring-properties" title="Permanent link">¶</a></h1>
<div class="codehilite"><pre>
</pre></div>
@@ -736,7 +747,7 @@ public class Implementation implements F
{center}
{div}
* <a href="/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/configuration-handler.html">Configuration Handler</a></p>
-<h1 id="postregistration-and-postunregistration-callbacks">PostRegistration and PostUnregistration callbacks</h1>
+<h1 id="postregistration-and-postunregistration-callbacks">PostRegistration and PostUnregistration callbacks<a class="headerlink" href="#postregistration-and-postunregistration-callbacks" title="Permanent link">¶</a></h1>
<ul>
<li>This feature is part of the provided service handler, and so requires that the component provides a service.</li>
<li>
@@ -761,7 +772,7 @@ public void unregistered(ServiceReferenc
<p><a href="http://felix.apache.org/site/providing-osgi-services.html#ProvidingOSGiservices-Beingnotifiedoftheserviceregistrationandunregistration">Provided Service Handler</a></p>
</li>
</ul>
-<h1 id="controlling-service-publication">Controlling service publication</h1>
+<h1 id="controlling-service-publication">Controlling service publication<a class="headerlink" href="#controlling-service-publication" title="Permanent link">¶</a></h1>
<ul>
<li>This feature is part of the provided service handler, and so requires that the component provides a service.</li>
<li>
@@ -781,7 +792,7 @@ private boolean controller</p>
<p><a href="http://felix.apache.org/site/providing-osgi-services.html">Provided Service Handler</a></p>
</li>
</ul>
-<h1 id="using-arch">Using 'arch'</h1>
+<h1 id="using-arch">Using 'arch'<a class="headerlink" href="#using-arch" title="Permanent link">¶</a></h1>
<ul>
<li>Deploy the 'arch' command bundle (available for Felix and Equinox)</li>
<li>
@@ -804,7 +815,7 @@ ipojo:handlers => list available hand
</li>
<li><a href="/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/architecture-handler.html">Architecture Handler</a></li>
</ul>
-<h1 id="temporal-dependencies">Temporal Dependencies</h1>
+<h1 id="temporal-dependencies">Temporal Dependencies<a class="headerlink" href="#temporal-dependencies" title="Permanent link">¶</a></h1>
<ul>
<li>Temporal dependencies are injected in fields. When accessing to the service, the thread waits for the service availability. If a timeout is reached, a timeout policy is executed.</li>
<li>Service objects can be injected as <code>proxies</code> and be given to collaborator objects.</li>
@@ -846,8 +857,8 @@ public class Implementation {</p>
{center}
{div}
* <a href="/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/temporal-service-dependency.html">Temporal Service Dependency</a></p>
-<h1 id="sending-and-receiving-events">Sending and receiving events</h1>
-<h2 id="receiving-events">Receiving events</h2>
+<h1 id="sending-and-receiving-events">Sending and receiving events<a class="headerlink" href="#sending-and-receiving-events" title="Permanent link">¶</a></h1>
+<h2 id="receiving-events">Receiving events<a class="headerlink" href="#receiving-events" title="Permanent link">¶</a></h2>
<ul>
<li>The event admin handler allows receiving events from the Event Admin.</li>
<li>The event admin handler is implemented as an <em>external handlers</em>. To use it, deploy and start the event admin handler bundle and an implementation of the event admin service.</li>
@@ -981,7 +992,7 @@ public class MyComponent {
</pre></div>
-<h1 id="extender-pattern">Extender Pattern</h1>
+<h1 id="extender-pattern">Extender Pattern<a class="headerlink" href="#extender-pattern" title="Permanent link">¶</a></h1>
<ul>
<li>Allows implementing an <code>Extender pattern</code> without handling obscure details</li>
<li>
@@ -1031,7 +1042,7 @@ public class Myextender {</p>
{center}
{div}
* <a href="/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/extender-pattern-handler.html">Extender Pattern Handler</a></p>
-<h1 id="whiteboard-pattern">Whiteboard Pattern</h1>
+<h1 id="whiteboard-pattern">Whiteboard Pattern<a class="headerlink" href="#whiteboard-pattern" title="Permanent link">¶</a></h1>
<ul>
<li>Allows implementing a <code>Whiteboard pattern</code> without handling obscure details</li>
<li>
@@ -1103,7 +1114,7 @@ public class WhiteBoardWIModification {<
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/ipojo-support.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/ipojo-support.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/ipojo-support.html Tue Sep 1 06:05:17 2015
@@ -171,13 +171,24 @@
<div class="container">
<div class="content">
- <h3 id="mailing-list">Mailing List</h3>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h3 id="mailing-list">Mailing List<a class="headerlink" href="#mailing-list" title="Permanent link">¶</a></h3>
<p>iPOJO is hosted as an Apache Felix sub-project, you can ask questions by sending mails to the Felix mailing lists. There is two mailing lists:
<em> The users mailing list
</em> The developer mailing list</p>
<p>Subscribe to the Felix users mailing list by sending a message to <a href="mailto:users-subscribe@felix.apache.org">users-subscribe@felix.apache.org</a>; after subscribing, email questions or feedback to <a href="mailto:users@felix.apache.org">users@felix.apache.org</a>.</p>
<p>Either, if you want to be involved, subscribe to the Felix dev mailing list by sending a message to <a href="mailto:dev-subscribe@felix.apache.org">dev-subscribe@felix.apache.org</a>; after subscribing, email ideas or feedback to <a href="mailto:dev@felix.apache.org">dev@felix.apache.org</a>.</p>
-<h3 id="bug-tracker">Bug Tracker</h3>
+<h3 id="bug-tracker">Bug Tracker<a class="headerlink" href="#bug-tracker" title="Permanent link">¶</a></h3>
<p>If you want a features, an improvement or report a bug, open an issue on the Apache Felix bug tracker:</p>
<ul>
<li>Go to the <a href="https://issues.apache.org/jira/browse/FELIX">https://issues.apache.org/jira/browse/FELIX</a> page</li>
@@ -202,7 +213,7 @@
may be trademarks or registered trademarks of their respective owners.
</div>
<div class="timestamp span3 offset2">
- Rev. 1464894 by clement on Fri, 5 Apr 2013 08:54:50 +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/related-works.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/related-works.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/related-works.html Tue Sep 1 06:05:17 2015
@@ -171,16 +171,27 @@
<div class="container">
<div class="content">
- <h1 id="presentations">Presentations</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="presentations">Presentations<a class="headerlink" href="#presentations" title="Permanent link">¶</a></h1>
<ul>
<li><a href="http://www.aqute.biz/resources/2005/2005-10-OSGIWC*Service*Blinder.ppt">Service Blinder</a> : Peter Kriens Presentation about "Removing Cruft" (OSGi World Congress 2005)</li>
</ul>
-<h1 id="articles">Articles</h1>
+<h1 id="articles">Articles<a class="headerlink" href="#articles" title="Permanent link">¶</a></h1>
<ul>
<li>Extending OSGi for Java Module Orientation</li>
<li><a href="http://www-adele.imag.fr/Les.Publications/intConferences/ICSE2004Cer.pdf">Autonomous Adaptation to Dynamic Availability Using a Service-Oriented Component Model </a></li>
</ul>
-<h1 id="web-sites">Web Sites</h1>
+<h1 id="web-sites">Web Sites<a class="headerlink" href="#web-sites" title="Permanent link">¶</a></h1>
<ul>
<li><a href="http://www.springframework.org/osgi">Spring-DM</a></li>
<li><a href="http://gravity.sourceforge.net/servicebinder/">Service Binder</a></li>
@@ -202,7 +213,7 @@
may be trademarks or registered trademarks of their respective owners.
</div>
<div class="timestamp span3 offset2">
- Rev. 1443051 by clement on Wed, 6 Feb 2013 16:33:33 +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-lightweight-http-service.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-lightweight-http-service.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-lightweight-http-service.html 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 Lightweight HTTP Service</h1>
- <h1 id="apache-felix-lightweight-http-service">Apache Felix Lightweight HTTP Service</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-lightweight-http-service">Apache Felix Lightweight HTTP Service<a class="headerlink" href="#apache-felix-lightweight-http-service" title="Permanent link">¶</a></h1>
<div class="toc">
<ul>
<li><a href="#apache-felix-lightweight-http-service">Apache Felix Lightweight HTTP Service</a><ul>
@@ -77,9 +99,9 @@
</ul>
</div>
<p>This is a <em>minimal</em> implementation of the HTTP Service Specification as described in chapter 102 of the OSGi Compendium. The goal is to provide a basic HTTP Service for resource-constrained devices and other use cases where the standard HTTP Service may be overkill. The bundle requires Java 1.4 or above and implements the Servlet 2.4 API.</p>
-<h2 id="targets">Targets</h2>
+<h2 id="targets">Targets<a class="headerlink" href="#targets" title="Permanent link">¶</a></h2>
<p>The Apache Felix Lightweight HTTP Service comes in two targets: core and complete. Core provides the minimal server functionality and requires the HTTP Servlet and OSGi HTTP Service APIs to be provided by other bundles at runtime. The complete bundle packages these as well and has no external dependencies. Currently the complete bundle is about 2x the size of core (55Kb vs 98Kb). If space is a concern and the API packages are already provided by other bundles in your environment, the core target makes the most sense. However for easy installation and maintenance, the complete bundle may be the better choice.</p>
-<h2 id="configuration-properties">Configuration Properties</h2>
+<h2 id="configuration-properties">Configuration Properties<a class="headerlink" href="#configuration-properties" title="Permanent link">¶</a></h2>
<p>The service can only be configured using OSGi environment properties. The service supports a subset of the standard HTTP Service properties:</p>
<ul>
<li><code>org.osgi.service.http.port</code> - The port used for servlets and resources available via HTTP. The default is <code>8080</code>.</li>
@@ -88,7 +110,7 @@
<li><code>felix.log.level</code> - The log level for messages originating from the bundle. The default is 1.</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-log.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-log.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-log.html 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 Log</h1>
- <h1 id="apache-felix-log">Apache Felix Log</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-log">Apache Felix Log<a class="headerlink" href="#apache-felix-log" title="Permanent link">¶</a></h1>
<p>The OSGi Service Compendium specification defines a general purpose Log Service for the OSGi Platform. It is a very simple specification that doesn't provide all the functionality commonly available in enterprise-level logging tools, but its extensible service model can be used to build fairly sophisticated logging solutions.</p>
<p>The Log Service specification defines four main entities:</p>
<ul>
@@ -75,7 +97,7 @@
<li><em><code>org.osgi.service.log.LogEntry</code></em> - interface defining a log entry.</li>
<li><em><code>org.osgi.service.log.LogListener</code></em> - interface defining a listener for log entries, which is notified about new log entries.</li>
</ul>
-<h2 id="accessing-the-log-service">Accessing the log service</h2>
+<h2 id="accessing-the-log-service">Accessing the log service<a class="headerlink" href="#accessing-the-log-service" title="Permanent link">¶</a></h2>
<p>To access a <code>LogService</code> instance it is necessary to look it up in the OSGi service registry as demonstrated in the following code snippet:</p>
<div class="codehilite"><pre><span class="n">public</span> <span class="n">class</span> <span class="n">Activator</span> <span class="n">implements</span> <span class="n">BundleActivator</span>
<span class="p">{</span>
@@ -95,7 +117,7 @@
<p>It is possible, and advisable, to use more sophisticated service acquisition mechanisms like a Service Tracker, Dynamic Services or iPOJO.</p>
-<h2 id="using-the-log-service">Using the log service</h2>
+<h2 id="using-the-log-service">Using the log service<a class="headerlink" href="#using-the-log-service" title="Permanent link">¶</a></h2>
<p>The <code>LogService</code> interface provides four methods for logging:</p>
<div class="codehilite"><pre><span class="n">public</span> <span class="n">interface</span> <span class="n">LogService</span>
<span class="p">{</span>
@@ -123,7 +145,7 @@
<li><code>LogService.LOG_WARNING</code></li>
<li><code>LogService.LOG_ERROR</code></li>
</ul>
-<h2 id="retrieving-log-entries">Retrieving log entries</h2>
+<h2 id="retrieving-log-entries">Retrieving log entries<a class="headerlink" href="#retrieving-log-entries" title="Permanent link">¶</a></h2>
<p>The <code>LogReaderService</code> provides a <code>getLog()</code> method to retrieve an <code>Enumeration</code> of the latest log entries. The following code snippets demonstrates how to retrieve it from the service registry and use it:</p>
<div class="codehilite"><pre><span class="n">ServiceReference</span> <span class="n">ref</span> <span class="p">=</span> <span class="n">context</span><span class="p">.</span><span class="n">getServiceReference</span><span class="p">(</span><span class="n">LogReaderService</span><span class="p">.</span><span class="n">class</span><span class="p">.</span><span class="n">getName</span><span class="p">());</span>
<span class="k">if</span> <span class="p">(</span><span class="n">ref</span> !<span class="p">=</span> <span class="n">null</span><span class="p">)</span>
@@ -134,7 +156,7 @@
</pre></div>
-<h2 id="creating-and-registering-a-loglistener">Creating and registering a <code>LogListener</code></h2>
+<h2 id="creating-and-registering-a-loglistener">Creating and registering a <code>LogListener</code><a class="headerlink" href="#creating-and-registering-a-loglistener" title="Permanent link">¶</a></h2>
<p>The Log Service specification doesn't define any particular entity to store, display, or write log entries; it's up to the developer to implement this functionality or to choose an available implementation capable of doing that. To create such a bundle, the first step is to create an implementation of the <code>LogListener</code> interface. The following code shows a simple implementation that echoes the log message:</p>
<div class="codehilite"><pre><span class="n">public</span> <span class="n">class</span> <span class="n">LogWriter</span> <span class="n">implements</span> <span class="n">LogListener</span>
<span class="p">{</span>
@@ -157,9 +179,9 @@
</pre></div>
-<h2 id="setup-of-apache-felix-log-service">Setup of Apache Felix Log Service</h2>
+<h2 id="setup-of-apache-felix-log-service">Setup of Apache Felix Log Service<a class="headerlink" href="#setup-of-apache-felix-log-service" title="Permanent link">¶</a></h2>
<p>The Apache Felix Log Service bundle doesn't have any specific dependency on Felix, so it can run on any OSGi container. For its configuration, it will use the following optional system properties:</p>
-<table>
+<table class="table">
<thead>
<tr>
<th>Property</th>
@@ -181,7 +203,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