felix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r849204 [22/33] - in /websites/staging/felix/trunk/content: ./ documentation/subprojects/ documentation/subprojects/apache-felix-ipojo/ documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-devguide/ documentation/subprojects/apac...
Date Sun, 03 Feb 2013 06:45:22 GMT
Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/service-requirement-handler.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/service-requirement-handler.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/service-requirement-handler.html Sun Feb  3 06:45:21 2013
@@ -20,9 +20,45 @@
   <head>
     <title>Apache Felix - Service Requirement Handler</title>
     <link rel="icon" href="/res/favicon.ico">
-    <link rel="stylesheet" href="/res/site.css" type="text/css" media="all">
-    <link rel="stylesheet" href="/res/codehilite.css" type="text/css" media="all">
+    <link rel="stylesheet" href="/site/media.data/site.css" type="text/css" media="all">
+    <link rel="stylesheet" href="/ipojo/site/superfish.css" type="text/css" media="all">
+    <link rel="stylesheet" href="/ipojo/site/style.css" type="text/css" media="all">
     <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
+    
+    <!--
+    <script class="javascript" src="http://cwiki.apache.org/confluence/download/resources/confluence.ext.code:code/shCore.js"></script>
+    <script class="javascript" src="http://cwiki.apache.org/confluence/download/resources/confluence.ext.code:code/shBrushCSharp.js"></script>
+    <script class="javascript" src="http://cwiki.apache.org/confluence/download/resources/confluence.ext.code:code/shBrushPhp.js"></script>
+    <script class="javascript" src="http://cwiki.apache.org/confluence/download/resources/confluence.ext.code:code/shBrushJScript.js"></script>
+    <script class="javascript" src="http://cwiki.apache.org/confluence/download/resources/confluence.ext.code:code/shBrushVb.js"></script>
+    <script class="javascript" src="http://cwiki.apache.org/confluence/download/resources/confluence.ext.code:code/shBrushSql.js"></script>
+    <script class="javascript" src="http://cwiki.apache.org/confluence/download/resources/confluence.ext.code:code/shBrushXml.js"></script>
+    <script class="javascript" src="http://cwiki.apache.org/confluence/download/resources/confluence.ext.code:code/shBrushShell.js"></script>
+    <script class="javascript" src="http://cwiki.apache.org/confluence/download/resources/confluence.ext.code:code/shBrushDelphi.js"></script>
+    <script class="javascript" src="http://cwiki.apache.org/confluence/download/resources/confluence.ext.code:code/shBrushPython.js"></script>
+    <script class="javascript" src="http://cwiki.apache.org/confluence/download/resources/confluence.ext.code:code/shBrushJava.js"></script>
+    -->
+    
+    <script type="text/javascript" src="/ipojo/site/jquery-1.js"></script>
+    <script type="text/javascript" src="/ipojo/site/hoverIntent.js"></script>
+    <script type="text/javascript" src="/ipojo/site/superfish.js"></script> 
+    <script type="text/javascript" src="/ipojo/site/supersubs.js"></script> 
+    
+    <script type="text/javascript"> 
+     
+        $(document).ready(function(){ 
+            $("ul.sf-menu").supersubs({ 
+                minWidth:    14,   // minimum width of sub-menus in em units 
+                maxWidth:    30,   // maximum width of sub-menus in em units 
+                extraWidth:  1     // extra width can ensure lines don't sometimes turn over 
+                                   // due to slight rounding differences and font-family 
+            }).superfish();  // call supersubs first, then superfish, so that subs are 
+                             // not display:none when measuring. Call before initialising 
+                             // containing tabs for same reason. 
+        }); 
+     
+    </script>
+    
   </head>
   <body>
     <div class="title">
@@ -37,277 +73,353 @@
         </a>
       </div>
     </div>
+  
+    <div class="main">
+    <div class="main">
+    <div class="page-header">
+    <img src="/ipojo/site/header.png" class="header">
+    <a href="http://ipojo.org"><img src="/ipojo/site/ipojo.png" width="225" class="header-logo"></a>
+    <ul class="sf-menu sf-js-enabled sf-shadow" id="ipojo-menu">
+    <li class="current">
+    <!-- Menu Overview -->
+    <a href="#" class="sf-with-ul">Overview<span class="sf-sub-indicator"> »</span><span class="sf-sub-indicator"> »</span></a>
+    <ul>
+        <li>
+        <a href="">Home</a>                          
+        </li>
+        <li>
+        <a href="">Why choose iPOJO</a>
+        </li>
+        <li>
+        <a href="">Success stories</a>
+        </li>
+        <li>
+        <a href="">Features</a>
+        </li>
+    </ul>
+    </li>   
     
-    <div class="menu"> 
-      <p><a href="/news.html">news</a>  <br />
-<a href="/license.html">license</a>  <br />
-<a href="/downloads.cgi">downloads</a>  <br />
-<a href="/documentation.html">documentation</a>  <br />
-<a href="/mailinglists.html">mailing lists</a>  <br />
-<a href="/documentation/community/contributing.html">contributing</a>  <br />
-<a href="/sitemap.html">site map</a>  <br />
-<a href="http://www.apache.org/">asf</a>  <br />
-<a href="http://www.apache.org/security/">security</a>  <br />
-<a href="http://www.apache.org/foundation/sponsorship.html">sponsorship</a>  <br />
-<a href="http://www.apache.org/foundation/thanks.html">sponsors</a>  <br />
-</p>
-<iframe
-    src="http://www.apache.org/ads/button.html"
-    style="border-width:0; float: left"
-    frameborder="0"
-    scrolling="no"
-    width="135"
-    height="135">
-</iframe>
-    </div>
+    <li class="">           
+    <!-- Menu download -->
+    <li>
+    <a href="/downloads.cgi">Download </a>
+    </li>
     
-    <div class="main">
-      <div class="breadcrump" style="font-size: 80%;">
-        <a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/documentation.html">Documentation</a>&nbsp;&raquo&nbsp;<a href="/documentation/subprojects.html">Apache Felix Subproject Documentation</a>&nbsp;&raquo&nbsp;<a href="/documentation/subprojects/apache-felix-ipojo.html">Apache Felix iPOJO</a>&nbsp;&raquo&nbsp;<a href="/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide.html">apache-felix-ipojo-userguide</a>&nbsp;&raquo&nbsp;<a href="/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components.html">Describing components</a>
-      </div>
-
+    <li class="">                   
+    <!-- Menu Documentation -->
+    <a href="#" class="sf-with-ul">Documentation<span class="sf-sub-indicator"> »</span><span class="sf-sub-indicator"> »</span></a>
+    <ul>
+        <!-- sub-menu : getting started -->
+        <li class="">
+        <a href="#" class="sf-with-ul">Getting Started<span class="sf-sub-indicator"> »</span><span class="sf-sub-indicator"> »</span></a>
+        <ul>
+         <li><a href="">iPOJO in 10 minutes</a></li>
+         <li><a href="">Using Annotations</a></li>
+         <li><a href="">Maven tutorial</a></li>
+         <li><a href="">Advanced tutorial</a></li>
+         <li><a href="">Using Distributed OSGi</a></li>
+         <li><a href="">Application Composition</a></li>
+        </ul>
+        </li> <!-- end of getting started -->
+        <!-- sub menu : Describing Components -->
+         <li class="">
+            <a href="" class="sf-with-ul">Describing components<span class="sf-sub-indicator"> »</span><span class="sf-sub-indicator"> »</span></a>
+            <ul>
+            <li><a href="">Requiring a service</a></li>
+            <li><a href="">Providing a service</a></li>
+            <li><a href="">Lifecycle management</a></li>
+            <li><a href="">Configuration</a></li>
+            <li><a href="">Introspection</a></li>
+            <li><a href="">Impacting the lifecycle</a></li>
+            <li><a href="">Asynchronous communication</a></li>
+            <li><a href="">JMX management</a></li>
+            <li><a href="">Extender pattern</a></li>
+            <li><a href="">Whiteboard pattern</a></li>
+            <li><a href="">Temporal dependencies</a></li>
+            </ul>
+         </li> <!-- End of describing components -->
+        <!-- sub-menu : User Guide -->
+        <li class="">
+        <a href="" class="sf-with-ul">User Guide<span class="sf-sub-indicator"> »</span><span class="sf-sub-indicator"> »</span></a>
+            <ul>
+            <li><a href="">iPOJO and config admin</a></li>
+            <li><a href="">Factories and Instances</a></li>
+            <li><a href="">XML Schemas</a></li>
+            <li><a href="">API</a></li>
+            <li><a href="">Testing components</a></li>
+            <li><a href="">Eclipse Integration</a></li>
+            <li><a href="">FAQ</a></li>
+            <li><a href="">Reference Card</a></li>
+            </ul>
+        </li> <!-- end of user guide -->
+        <!-- sub-menu : Dev Guide -->
+        <li> 
+        <a href="#" class="sf-with-ul">Advanced Topics<span class="sf-sub-indicator"> »</span><span class="sf-sub-indicator"> »</span></a>
+           <ul>
+            <li><a href="http://felix.apache.org/ipojo/api/1.6.0">Javadoc</a></li>
+            <li><a href="">Handler development</a></li>
+            <li><a href="">Manipulation Metadata </a></li>
+            <li><a href="">Dive into the iPOJO Manipulation depths</a></li>
+           </ul>
+        </li> <!-- End of Dev guide -->
+    </ul> 
+    </li> <!-- End of doc -->
+    <!-- Menu 4 : Tools -->
+    <li class="">
+    <a href="#" class="sf-with-ul">Tools<span class="sf-sub-indicator"> »</span><span class="sf-sub-indicator"> »</span></a>
+    <ul>
+       <li><a href="">Ant Task</a></li>
+       <li><a href="">Eclipse Plugin</a></li>
+       <li><a href="">Maven Plugin</a></li>
+       <li><a href="">`arch` shell command</a></li>
+       <li><a href="">Online Manipulator</a></li>
+       <li><a href="">Webconsole plugin</a></li>
+       <li><a href="">Junit4OSGi</a></li>
+    </ul>   
+    </li><!-- End of tools -->  
+    <!-- Menu 5 : Support -->
+    <li>
+    <a href="">Support </a>
+    </li>
+    <!-- End of the menu 5 -->          
+    <!-- Menu 6 : Misc -->
+    <li class="">
+    <a href="#" class="sf-with-ul">Misc<span class="sf-sub-indicator"> »</span><span class="sf-sub-indicator"> »</span></a>
+    <ul>
+       <li><a href="">Supported JVMs</a></li>
+       <li><a href="">Supported OSGi Implementations</a></li>
+       <li><a href="http://ipojo-dark-side.blogspot.com">iPOJO's Dark Side Blog</a></li>
+       <li><a href="">Article & Presentations</a></li>
+       <li><a href="http://www.apache.org/">ASF</a></li>
+       <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
+       <li><a href="http://www.apache.org/foundation/thanks.html">Sponsors</a></li>
+    </ul>
+    </li><!-- End of misc -->
+    </ul> <!-- End of the menu -->
+    </div> <!-- Page header -->
+  
+      <!-- 
       
       <div class="tip">
            This page is a translated version of <a href="/site/service-requirement-handler.html" target="felix_cwiki">/site/service-requirement-handler.html</a>. In case of
            doubt you might want to refer to the old page.
       </div>
       
+      -->
       
       <h1>Service Requirement Handler</h1>
-      <p>{include:apache-felix-ipojo-header}</p>
-<div class="content">
-
-# Service Dependency Management
-
-*One of the main iPOJO feature is the service injection. So, a component can consume a service without managing the service discovery, tracking and binding. iPOJO manages all these interactions and injects required service into the component. This page explains how to use services.*
-
-{div:class=toc}
+      
+      <div class="content">
+        <h1 id="service-dependency-management">Service Dependency Management</h1>
+<p><em>One of the main iPOJO feature is the service injection. So, a component can consume a service without managing the service discovery, tracking and binding. iPOJO manages all these interactions and injects required service into the component. This page explains how to use services.</em></p>
+<p>{div:class=toc}
 [TOC]
-{div}
-
-## Service Requirement
-
-### What's a service requirement?
-
-A requirement represents a required service. Therefore, it manages the service lookup and the service binding. When an instance requires a service, the handler injects directly a service object inside a field, or invokes a method when a consistent service appears (or disappears). Service requirements can be:
-* Simple / Aggregate : the component can require      one or several service providers
-* Mandatory / Optional : a component can declare an      optional dependency
-* Filtered : a component can filter available      providers
-* Dynamic / Static / Dynamic-Priority : the      component can specify the binding policy
-* Specific : the dependency targets a specific service provider
-* Proxy : by default, iPOJO injects a smart proxy, but it can also be a dynamic proxy or the direct references
-
-### Dynamism & Instance Lifecycle
-
-In OSGi™, services can appear and disappear dynamically. This implies dependencies can target a provider which can appear or disappear dynamically. So, dependencies need to manage this dynamism by tracking every time available services. At any moment, a dependency can be unresolved (i.e. no more provider can fulfill the requirement). In the case of a mandatory requirement, the instance becomes invalid (an invalid instance is no more accessible externally, for example provided services are unpublished). If a service, resolving the unfilled dependency appears, the instance becomes valid. In consequence, dependencies affect directly the instance state, and must manage correctly OSGi dynamism to allow a complete unloading when a service goes away. As soon a mandatory dependency cannot be fulfilled, the instance is invalidated.
-
-By default, dependencies are managed dynamically (as previously explained). However, iPOJO supports two other types of binding policies:
-* Static : if a bound service disappears, the instance is invalidated and cannot be revalidated (binding broken forever)
-* Dynamic-Priority: at each injection, the *best* provider is injected, or the providers array is sorted according to the OSGi Ranking policy or to a specified sorting algorithm.
-
-## Service Requirement Injection Mechanisms
-
-iPOJO support several types of injections:
-* Field injection: a field contains the service object. As soon as the field is used, a consistent service object is      injected. This injection type fully hides the dynamism
-
-    @Requires
-    private LogService log;
-
-* Method invocation: when a service appears, or disappears a method in the component is invoked. For each dependency, bind / unbind / modified methods are invoked to notify the component of the event.
-
-    @Bind
-    public void bindLogService(LogService log) { /*...*/ }
-    @Unbind
-    public void unbindLogService(LogService log) { /*...*/ }
-    @Modified
-    public void modifiedLogService(LogService log) { /*...*/ }
-
-* Constructor injection: services can also be injected as constructor parameter (only if proxies are enabled). *1.7.0-SNAPSHOT*
-
-    public MyComponent(@Requires LogService log) { /*...*/ }
-
-Moreover, the injections types can be mixed. A component can declare a requirement containing both a field and 'binding' methods.
-
-### Field injection
-
-Let's imagine a Hello service with one method 'getMessage' returning a "Hello Message". The following component implementation can use this service by attaching this service to a field and by using the field:
+{div}</p>
+<h2 id="service-requirement">Service Requirement</h2>
+<h3 id="whats-a-service-requirement">What's a service requirement?</h3>
+<p>A requirement represents a required service. Therefore, it manages the service lookup and the service binding. When an instance requires a service, the handler injects directly a service object inside a field, or invokes a method when a consistent service appears (or disappears). Service requirements can be:
+<em> Simple / Aggregate : the component can require      one or several service providers
+</em> Mandatory / Optional : a component can declare an      optional dependency
+<em> Filtered : a component can filter available      providers
+</em> Dynamic / Static / Dynamic-Priority : the      component can specify the binding policy
+<em> Specific : the dependency targets a specific service provider
+</em> Proxy : by default, iPOJO injects a smart proxy, but it can also be a dynamic proxy or the direct references</p>
+<h3 id="dynamism-instance-lifecycle">Dynamism &amp; Instance Lifecycle</h3>
+<p>In OSGi™, services can appear and disappear dynamically. This implies dependencies can target a provider which can appear or disappear dynamically. So, dependencies need to manage this dynamism by tracking every time available services. At any moment, a dependency can be unresolved (i.e. no more provider can fulfill the requirement). In the case of a mandatory requirement, the instance becomes invalid (an invalid instance is no more accessible externally, for example provided services are unpublished). If a service, resolving the unfilled dependency appears, the instance becomes valid. In consequence, dependencies affect directly the instance state, and must manage correctly OSGi dynamism to allow a complete unloading when a service goes away. As soon a mandatory dependency cannot be fulfilled, the instance is invalidated.</p>
+<p>By default, dependencies are managed dynamically (as previously explained). However, iPOJO supports two other types of binding policies:
+<em> Static : if a bound service disappears, the instance is invalidated and cannot be revalidated (binding broken forever)
+</em> Dynamic-Priority: at each injection, the <em>best</em> provider is injected, or the providers array is sorted according to the OSGi Ranking policy or to a specified sorting algorithm.</p>
+<h2 id="service-requirement-injection-mechanisms">Service Requirement Injection Mechanisms</h2>
+<p>iPOJO support several types of injections:
+* Field injection: a field contains the service object. As soon as the field is used, a consistent service object is      injected. This injection type fully hides the dynamism</p>
+<div class="codehilite"><pre><span class="nv">@Requires</span>
+<span class="n">private</span> <span class="n">LogService</span> <span class="nb">log</span><span class="p">;</span>
+</pre></div>
+
+
+<ul>
+<li>
+<p>Method invocation: when a service appears, or disappears a method in the component is invoked. For each dependency, bind / unbind / modified methods are invoked to notify the component of the event.</p>
+<p>@Bind
+public void bindLogService(LogService log) { /<em>...</em>/ }
+@Unbind
+public void unbindLogService(LogService log) { /<em>...</em>/ }
+@Modified
+public void modifiedLogService(LogService log) { /<em>...</em>/ }</p>
+</li>
+<li>
+<p>Constructor injection: services can also be injected as constructor parameter (only if proxies are enabled). <em>1.7.0-SNAPSHOT</em></p>
+<p>public MyComponent(@Requires LogService log) { /<em>...</em>/ }</p>
+</li>
+</ul>
+<p>Moreover, the injections types can be mixed. A component can declare a requirement containing both a field and 'binding' methods.</p>
+<h3 id="field-injection">Field injection</h3>
+<p>Let's imagine a Hello service with one method 'getMessage' returning a "Hello Message". The following component implementation can use this service by attaching this service to a field and by using the field:
 {code:java}
 @Component
 @Instantiate
 public class HelloConsumer {
     @Requires
-    private Hello m_hello;
+    private Hello m_hello;</p>
+<div class="codehilite"><pre><span class="n">public</span> <span class="n">doSomething</span><span class="p">()</span> <span class="p">{</span>
+    <span class="n">System</span><span class="o">.</span><span class="n">out</span><span class="o">.</span><span class="n">println</span><span class="p">(</span><span class="n">m_hello</span><span class="o">.</span><span class="n">getMesage</span><span class="p">());</span>
+<span class="p">}</span>
+</pre></div>
 
-    public doSomething() {
-        System.out.println(m_hello.getMesage());
-    }
-}
-
-    You can also use XML to describe this component type:
-    {code:xml}
-    <component classname="...HelloConsumer">
-        <requires field="m_hello"/>
-        ...
-    </component>
-
-The metadata contains a 'requires' element (representing the service dependency) and specify a field used to inject the service. The implementation uses the field as a normal field without managing service interactions.
-
-### Method invocation
-
-The second injection mechanism uses methods in the implementation class. By this way, the dynamics can be managed directly by the developer. Each dependency can declare three methods:
-* A bind method called when a service appears
-* An unbind method called when a service disappears
-* A modified method called when a service is modified (the service properties changed, but the service still matches the requirement)
-
-Moreover, callbacks can be in the component super class (in this case methods must be public). These methods can have one of these four signatures:
-* Without any argument: the method is just a  notification (method())
-* With the service object : the object is the  implicated service object (method(Service svc))
-* With an OSGi service reference: the service  reference appearing or disappearing (method(ServiceReference ref))
-* With the service object and the OSGi service reference (method(Service svc, ServiceReference ref))
-* With the service object and the service properties inside a Map (method(Service svc, Map properties))
-* With the service object and the service properties inside a Dictionary (method(Service svc, Dictionary properties))
 
-The following component implementation shows an example of implementation using this mechanism:
+<p>}</p>
+<div class="codehilite"><pre>You can also use XML to describe this component type:
+{code:xml}
+<span class="nt">&lt;component</span> <span class="na">classname=</span><span class="s">&quot;...HelloConsumer&quot;</span><span class="nt">&gt;</span>
+    <span class="nt">&lt;requires</span> <span class="na">field=</span><span class="s">&quot;m_hello&quot;</span><span class="nt">/&gt;</span>
+    ...
+<span class="nt">&lt;/component&gt;</span>
+</pre></div>
+
+
+<p>The metadata contains a 'requires' element (representing the service dependency) and specify a field used to inject the service. The implementation uses the field as a normal field without managing service interactions.</p>
+<h3 id="method-invocation">Method invocation</h3>
+<p>The second injection mechanism uses methods in the implementation class. By this way, the dynamics can be managed directly by the developer. Each dependency can declare three methods:
+<em> A bind method called when a service appears
+</em> An unbind method called when a service disappears
+* A modified method called when a service is modified (the service properties changed, but the service still matches the requirement)</p>
+<p>Moreover, callbacks can be in the component super class (in this case methods must be public). These methods can have one of these four signatures:
+<em> Without any argument: the method is just a  notification (method())
+</em> With the service object : the object is the  implicated service object (method(Service svc))
+<em> With an OSGi service reference: the service  reference appearing or disappearing (method(ServiceReference ref))
+</em> With the service object and the OSGi service reference (method(Service svc, ServiceReference ref))
+<em> With the service object and the service properties inside a Map (method(Service svc, Map properties))
+</em> With the service object and the service properties inside a Dictionary (method(Service svc, Dictionary properties))</p>
+<p>The following component implementation shows an example of implementation using this mechanism:
 {code:java}
 @Component
 public class HelloConsumer {
-  private Hello m_hello;
-
-  @Bind
+  private Hello m_hello;</p>
+<p>@Bind
   public void bindHello(Hello h) { m_hello = h; }
   @Unbind
   public void unbindHello() { m_hello = null; }
   public doSomething() { System.out.println(m_hello.getMesage()); }
-}
-
-    The  callback is not mandatory. The following XML metadata are describing the same component type:
-    {code:xml}
-    <component classname="...HelloConsumer">
-    <requires>
-        <callback type="bind" method="bindHello">
-        <callback type="unbind" method="unbindHello">
-    </requires>
-    ...
-    </component>
-
-Note, that the different callbacks can be have different signatures. By using this mechanism, you need to be sure to manage the dynamism correctly.
-([See note on type discovery]())
-
-Using the @Modified callback is also quite simple:
+}</p>
+<div class="codehilite"><pre>The  callback is not mandatory. The following XML metadata are describing the same component type:
+{code:xml}
+<span class="nt">&lt;component</span> <span class="na">classname=</span><span class="s">&quot;...HelloConsumer&quot;</span><span class="nt">&gt;</span>
+<span class="nt">&lt;requires&gt;</span>
+    <span class="nt">&lt;callback</span> <span class="na">type=</span><span class="s">&quot;bind&quot;</span> <span class="na">method=</span><span class="s">&quot;bindHello&quot;</span><span class="nt">&gt;</span>
+    <span class="nt">&lt;callback</span> <span class="na">type=</span><span class="s">&quot;unbind&quot;</span> <span class="na">method=</span><span class="s">&quot;unbindHello&quot;</span><span class="nt">&gt;</span>
+<span class="nt">&lt;/requires&gt;</span>
+...
+<span class="nt">&lt;/component&gt;</span>
+</pre></div>
+
+
+<p>Note, that the different callbacks can be have different signatures. By using this mechanism, you need to be sure to manage the dynamism correctly.
+(<a href="">See note on type discovery</a>)</p>
+<p>Using the @Modified callback is also quite simple:
 {code:java}
 @Component
 public class HelloConsumer {
-  private Hello m_hello;
-
-  @Bind
+  private Hello m_hello;</p>
+<p>@Bind
   public void bindHello(Hello h) { m_hello = h; }
   @Unbind
   public void unbindHello() { m_hello = null; }
   @Modified
-  public void modifiedHello() { /* ... */ }
-  public doSomething() { System.out.println(m_hello.getMesage()); }
-
-}
+  public void modifiedHello() { /<em> ... </em>/ }
+  public doSomething() { System.out.println(m_hello.getMesage()); }</p>
+<p>}</p>
+<div class="codehilite"><pre><span class="n">h3</span><span class="o">.</span> <span class="n">Using</span> <span class="n">constructor</span> <span class="n">injection</span> <span class="p">(</span><span class="o">*</span><span class="mf">1.7.0</span><span class="o">-</span><span class="n">SNAPSHOT</span><span class="o">*</span><span class="p">)</span>
+<span class="n">Services</span> <span class="n">can</span> <span class="n">also</span> <span class="n">be</span> <span class="n">injected</span> <span class="n">using</span> <span class="n">constructor</span> <span class="n">parameters:</span>
+</pre></div>
 
-    h3. Using constructor injection (*1.7.0-SNAPSHOT*)
-    Services can also be injected using constructor parameters:
 
-@Component
+<p>@Component
 public class MyComponent {
-    private LogService log;
-
-    public MyComponent(@Requires LogService log) {
-        this.log = log;
-    }
-}
-
-    h3. Mixing injections types
-
-    The different mechanisms can be used together. In this case, the field receives the value before the bind method invocation. Constructor parameters get their values during the constructor invocation. So, if the field is used in the method, the returned value will be up to date. The following component implementation uses this mechanism:
-    {code:java}
-    public class HelloConsumer {
-         @Requires(id="hello")
-         private Hello m_hello; // Injected Field
-
-         @Bind(id="hello")
-         public void bindHello() { System.out.println("Hello appears"); }
-         @Unbind(id="hello")
-         public void unbindHello() { System.out.println("Hello disapears"); }
-
-         public doSomething() { System.out.println(m_hello.getMesage()); }
-    }
-
-In XML, it results in:
-
-    <component classname="...HelloConsumer">
-        <requires  field="m_hello">
-            <callback type="bind" method="bindHello">
-            <callback type="unbind" method="unbindHello">
-        </requires>
-        ...
-    </component>
-
-The `id` attribute is used to determine which callbacks / fields go together. If ommitted, it is computed automaticcally:
-* for field it uses the field type.
-* for method starting with `bind` / `unbind` / `modified`, it extract the end of the method name (`bindFoo => Foo`)
-* for constructor parameter, it uses the parameter index
-
-So, it is strongly recommended to specify the id manually. 
-
-### Injection mechanisms & lazy object creation
-
-iPOJO creates objects only when required. When needed, iPOJO invokes the constructor of the implementation class. The implementation class can use field requirement because values are already injected and obviously constructor parameters. However, method dependencies are called *after* the constructor. If the service is available before the constructor call, the invocation of the bind methods is delayed until the a component class object is created.
-
-## Examples
-
-For all examples both annotations and XML forms are given. Just choose what you'd like to use.
-
-### Simple Requirement
-
-By default, a requirement is mandatory, non-filtered and simple (non-aggregate). The previous examples illustrate this kind of dependency. When services goes away and appears, the service substitution is hidden. Fields attached to simple requirement point always a consistent service object. For a simple dependency, the bind method is called once time when the service appears or just after the POJO constructor invocation is the service is available. When the service disappears the unbind method is called. The bind method is re-invoked as soon as another service provider is available. This invocation occurs immediately if another service provider if available. In this case, the instance is not invalidated.
-
-### Aggregate Requirement
-
-When a component requires several providers of the same service, it declares an aggregate dependency.
+    private LogService log;</p>
+<div class="codehilite"><pre><span class="n">public</span> <span class="n">MyComponent</span><span class="p">(</span><span class="nv">@Requires</span> <span class="n">LogService</span> <span class="nb">log</span><span class="p">)</span> <span class="p">{</span>
+    <span class="n">this</span><span class="o">.</span><span class="nb">log</span> <span class="o">=</span> <span class="nb">log</span><span class="p">;</span>
+<span class="p">}</span>
+</pre></div>
+
+
+<p>}</p>
+<div class="codehilite"><pre><span class="n">h3</span><span class="o">.</span> <span class="n">Mixing</span> <span class="n">injections</span> <span class="n">types</span>
+
+<span class="n">The</span> <span class="n">different</span> <span class="n">mechanisms</span> <span class="n">can</span> <span class="n">be</span> <span class="n">used</span> <span class="n">together</span><span class="o">.</span> <span class="n">In</span> <span class="n">this</span> <span class="k">case</span><span class="p">,</span> <span class="n">the</span> <span class="n">field</span> <span class="n">receives</span> <span class="n">the</span> <span class="n">value</span> <span class="n">before</span> <span class="n">the</span> <span class="nb">bind</span> <span class="n">method</span> <span class="n">invocation</span><span class="o">.</span> <span class="n">Constructor</span> <span class="n">parameters</span> <span class="n">get</span> <span class="n">their</span> <span class="nb">values</span> <span class="n">during</span> <span class="n">the</span> <span class="n">constructor</span> <span class="n">invocation</span><span class="o">.</span> <span class="n">So</span><sp
 an class="p">,</span> <span class="k">if</span> <span class="n">the</span> <span class="n">field</span> <span class="n">is</span> <span class="n">used</span> <span class="n">in</span> <span class="n">the</span> <span class="n">method</span><span class="p">,</span> <span class="n">the</span> <span class="n">returned</span> <span class="n">value</span> <span class="n">will</span> <span class="n">be</span> <span class="n">up</span> <span class="n">to</span> <span class="n">date</span><span class="o">.</span> <span class="n">The</span> <span class="n">following</span> <span class="n">component</span> <span class="n">implementation</span> <span class="n">uses</span> <span class="n">this</span> <span class="n">mechanism:</span>
+<span class="p">{</span><span class="n">code:java</span><span class="p">}</span>
+<span class="n">public</span> <span class="n">class</span> <span class="n">HelloConsumer</span> <span class="p">{</span>
+     <span class="nv">@Requires</span><span class="p">(</span><span class="n">id</span><span class="o">=</span><span class="s">&quot;hello&quot;</span><span class="p">)</span>
+     <span class="n">private</span> <span class="n">Hello</span> <span class="n">m_hello</span><span class="p">;</span> <span class="sr">//</span> <span class="n">Injected</span> <span class="n">Field</span>
+
+     <span class="nv">@Bind</span><span class="p">(</span><span class="n">id</span><span class="o">=</span><span class="s">&quot;hello&quot;</span><span class="p">)</span>
+     <span class="n">public</span> <span class="n">void</span> <span class="n">bindHello</span><span class="p">()</span> <span class="p">{</span> <span class="n">System</span><span class="o">.</span><span class="n">out</span><span class="o">.</span><span class="n">println</span><span class="p">(</span><span class="s">&quot;Hello appears&quot;</span><span class="p">);</span> <span class="p">}</span>
+     <span class="nv">@Unbind</span><span class="p">(</span><span class="n">id</span><span class="o">=</span><span class="s">&quot;hello&quot;</span><span class="p">)</span>
+     <span class="n">public</span> <span class="n">void</span> <span class="n">unbindHello</span><span class="p">()</span> <span class="p">{</span> <span class="n">System</span><span class="o">.</span><span class="n">out</span><span class="o">.</span><span class="n">println</span><span class="p">(</span><span class="s">&quot;Hello disapears&quot;</span><span class="p">);</span> <span class="p">}</span>
+
+     <span class="n">public</span> <span class="n">doSomething</span><span class="p">()</span> <span class="p">{</span> <span class="n">System</span><span class="o">.</span><span class="n">out</span><span class="o">.</span><span class="n">println</span><span class="p">(</span><span class="n">m_hello</span><span class="o">.</span><span class="n">getMesage</span><span class="p">());</span> <span class="p">}</span>
+<span class="p">}</span>
+</pre></div>
+
+
+<p>In XML, it results in:</p>
+<div class="codehilite"><pre><span class="nt">&lt;component</span> <span class="na">classname=</span><span class="s">&quot;...HelloConsumer&quot;</span><span class="nt">&gt;</span>
+    <span class="nt">&lt;requires</span>  <span class="na">field=</span><span class="s">&quot;m_hello&quot;</span><span class="nt">&gt;</span>
+        <span class="nt">&lt;callback</span> <span class="na">type=</span><span class="s">&quot;bind&quot;</span> <span class="na">method=</span><span class="s">&quot;bindHello&quot;</span><span class="nt">&gt;</span>
+        <span class="nt">&lt;callback</span> <span class="na">type=</span><span class="s">&quot;unbind&quot;</span> <span class="na">method=</span><span class="s">&quot;unbindHello&quot;</span><span class="nt">&gt;</span>
+    <span class="nt">&lt;/requires&gt;</span>
+    ...
+<span class="nt">&lt;/component&gt;</span>
+</pre></div>
 
-#### Aggregate Dependency with field injection
 
-{code:java}
+<p>The <code>id</code> attribute is used to determine which callbacks / fields go together. If ommitted, it is computed automaticcally:
+<em> for field it uses the field type.
+</em> for method starting with <code>bind</code> / <code>unbind</code> / <code>modified</code>, it extract the end of the method name (<code>bindFoo =&gt; Foo</code>)
+* for constructor parameter, it uses the parameter index</p>
+<p>So, it is strongly recommended to specify the id manually. </p>
+<h3 id="injection-mechanisms-lazy-object-creation">Injection mechanisms &amp; lazy object creation</h3>
+<p>iPOJO creates objects only when required. When needed, iPOJO invokes the constructor of the implementation class. The implementation class can use field requirement because values are already injected and obviously constructor parameters. However, method dependencies are called <em>after</em> the constructor. If the service is available before the constructor call, the invocation of the bind methods is delayed until the a component class object is created.</p>
+<h2 id="examples">Examples</h2>
+<p>For all examples both annotations and XML forms are given. Just choose what you'd like to use.</p>
+<h3 id="simple-requirement">Simple Requirement</h3>
+<p>By default, a requirement is mandatory, non-filtered and simple (non-aggregate). The previous examples illustrate this kind of dependency. When services goes away and appears, the service substitution is hidden. Fields attached to simple requirement point always a consistent service object. For a simple dependency, the bind method is called once time when the service appears or just after the POJO constructor invocation is the service is available. When the service disappears the unbind method is called. The bind method is re-invoked as soon as another service provider is available. This invocation occurs immediately if another service provider if available. In this case, the instance is not invalidated.</p>
+<h3 id="aggregate-requirement">Aggregate Requirement</h3>
+<p>When a component requires several providers of the same service, it declares an aggregate dependency.</p>
+<h4 id="aggregate-dependency-with-field-injection">Aggregate Dependency with field injection</h4>
+<p>{code:java}
 @Component
 public class HelloConsumer {
      @Requires
-     private Hello m_hellos[](); // Array => Aggregate
+     private Hello m_hellos<a href=""></a>; // Array =&gt; Aggregate
      public doSomething() {
-             for(int I = 0; I < m_hellos.length; i++) { 
-                 System.out.println(m_hellos[i]().getMessage());
+             for(int I = 0; I &lt; m_hellos.length; i++) { 
+                 System.out.println(m_hellos<a href="">i</a>.getMessage());
              }
        }
-}
-
-    For this component, XML metadata could be:
-    {code:xml}
-    <component classname="...HelloConsumer">
-        <requires field="m_hellos"/>
-        ...
-    </component>
-
-To declare an aggregate field for field requirement, you only need to declare an array (instead of a scalar type). iPOJO will create and inject the service object array. iPOJO discover that the dependency is aggregate during the bytecode introspection.
+}</p>
+<div class="codehilite"><pre>For this component, XML metadata could be:
+{code:xml}
+<span class="nt">&lt;component</span> <span class="na">classname=</span><span class="s">&quot;...HelloConsumer&quot;</span><span class="nt">&gt;</span>
+    <span class="nt">&lt;requires</span> <span class="na">field=</span><span class="s">&quot;m_hellos&quot;</span><span class="nt">/&gt;</span>
+    ...
+<span class="nt">&lt;/component&gt;</span>
+</pre></div>
 
-Array types cannot be 'proxied'. Moreover array dependencies cannot be injected as constructor parameter.
 
+<p>To declare an aggregate field for field requirement, you only need to declare an array (instead of a scalar type). iPOJO will create and inject the service object array. iPOJO discover that the dependency is aggregate during the bytecode introspection.</p>
+<p>Array types cannot be 'proxied'. Moreover array dependencies cannot be injected as constructor parameter.</p>
 <div class="info" markdown="1">
 **Synchronization**
 The synchronization is managed by iPOJO. As soon as you are 'touching' a dependency in a method, iPOJO ensure that you will keep these objects until the end of the method. Nested methods will share the same service object set.
 </div>
 
-#### Aggregate Dependency with field injection: list, vector, collection and set
-It is also possible to inject service objects inside fields of the type:
-* list
-* vector
-* collection
-* set
-
-{code:java}
+<h4 id="aggregate-dependency-with-field-injection-list-vector-collection-and-set">Aggregate Dependency with field injection: list, vector, collection and set</h4>
+<p>It is also possible to inject service objects inside fields of the type:
+<em> list
+</em> vector
+<em> collection
+</em> set</p>
+<p>{code:java}
 @Component
 public class HelloConsumer {
      @Requires(specification="org.apache.felix.ipojo.example.Hello")
@@ -317,17 +429,17 @@ public class HelloConsumer {
                  System.out.println(h).getMessage());
              }
        }
-}
-
-    For this component, XML metadata could be:
-    {code:xml}
-    <component classname="...HelloConsumer">
-        <requires field="m_hellos" specification="org.apache.felix.ipojo.example.Hello"/>
-        ...
-    </component>
+}</p>
+<div class="codehilite"><pre>For this component, XML metadata could be:
+{code:xml}
+<span class="nt">&lt;component</span> <span class="na">classname=</span><span class="s">&quot;...HelloConsumer&quot;</span><span class="nt">&gt;</span>
+    <span class="nt">&lt;requires</span> <span class="na">field=</span><span class="s">&quot;m_hellos&quot;</span> <span class="na">specification=</span><span class="s">&quot;org.apache.felix.ipojo.example.Hello&quot;</span><span class="nt">/&gt;</span>
+    ...
+<span class="nt">&lt;/component&gt;</span>
+</pre></div>
 
-In this case, just use the supported type that you want. iPOJO will automatically understand that it is an aggregate dependency, and will create the collection object containing service objects. However, you must specify the service specification. Indeed, generics types cannot be discovered at runtime reliably. 
 
+<p>In this case, just use the supported type that you want. iPOJO will automatically understand that it is an aggregate dependency, and will create the collection object containing service objects. However, you must specify the service specification. Indeed, generics types cannot be discovered at runtime reliably. </p>
 <div class="info" markdown="1">
 **Service specification discovery**
 The service specification (i.e. interface) cannot be discovered when using these types as the bytecode does not provide enough information. So, you have to indicate the required service interface (with the 'specification' attribute) in the requirement description.
@@ -338,9 +450,8 @@ The service specification (i.e. interfac
 As in the previous case, the synchronization is managed by iPOJO. As soon as you are *touching* a dependency in a method, iPOJO ensure that you will keep these objects until the end of the method. Nested methods will share the same service object set.
 </div>
 
-#### Aggregate Dependency with callbacks
-
-{code:java}
+<h4 id="aggregate-dependency-with-callbacks">Aggregate Dependency with callbacks</h4>
+<p>{code:java}
 public class HelloConsumer {
       private List m_hellos = new ArrayList();
       @Bind(aggregate=true)
@@ -353,324 +464,322 @@ public class HelloConsumer {
                   }
                 }
         }
-}
-
-    This dependency can also be described in XML as follow:
-    {code:xml}
-    <requires  aggregate="true">
-        <callback type="bind" method="bindHello">
-        <callback type="unbind" method="unbindHello">
-    </requires>
+}</p>
+<div class="codehilite"><pre>This dependency can also be described in XML as follow:
+{code:xml}
+<span class="nt">&lt;requires</span>  <span class="na">aggregate=</span><span class="s">&quot;true&quot;</span><span class="nt">&gt;</span>
+    <span class="nt">&lt;callback</span> <span class="na">type=</span><span class="s">&quot;bind&quot;</span> <span class="na">method=</span><span class="s">&quot;bindHello&quot;</span><span class="nt">&gt;</span>
+    <span class="nt">&lt;callback</span> <span class="na">type=</span><span class="s">&quot;unbind&quot;</span> <span class="na">method=</span><span class="s">&quot;unbindHello&quot;</span><span class="nt">&gt;</span>
+<span class="nt">&lt;/requires&gt;</span>
+</pre></div>
 
-In this case, iPOJO cannot detect if the dependency is aggregate or not. So, you need to add the '*aggregate*' attribute. The bindHello and unbindHello will be called each time a Hello service appears or disappears.
 
+<p>In this case, iPOJO cannot detect if the dependency is aggregate or not. So, you need to add the '<em>aggregate</em>' attribute. The bindHello and unbindHello will be called each time a Hello service appears or disappears.</p>
 <div class="info" markdown="1">
 **Synchronization**
 To avoid the list modification during the loop, you need synchronized the block. Indeed, as the field is not an iPOJO requirement, iPOJO will not manage the synchronization.
 </div>
 
-### Optional Requirement (Scalar)
-
-An optional requirement does not invalidate the instance despite no providers are available. Moreover, it is possible to inject a default service implementation when no *real* providers are available.
-
-#### Optional Requirement with field injection
-
-{code:java}
+<h3 id="optional-requirement-scalar">Optional Requirement (Scalar)</h3>
+<p>An optional requirement does not invalidate the instance despite no providers are available. Moreover, it is possible to inject a default service implementation when no <em>real</em> providers are available.</p>
+<h4 id="optional-requirement-with-field-injection">Optional Requirement with field injection</h4>
+<p>{code:java}
 @Component
 public class HelloConsumer {
          @Requires(optional=true)
-         private Hello m_hello;
+         private Hello m_hello;</p>
+<div class="codehilite"><pre>     <span class="n">public</span> <span class="n">doSomething</span><span class="p">()</span> <span class="p">{</span>  
+        <span class="n">System</span><span class="o">.</span><span class="n">out</span><span class="o">.</span><span class="n">println</span><span class="p">(</span><span class="n">m_hello</span><span class="o">.</span><span class="n">getMesage</span><span class="p">());</span>  
+     <span class="p">}</span>
+</pre></div>
 
-         public doSomething() {  
-            System.out.println(m_hello.getMesage());  
-         }
-}
-
-    For this component, equivalent XML metadata could be:
-    {code:xml}
-    <component classname="...HelloConsumer">
-        <requires field="m_hello" optional="true"/>
-        ...
-    </component>
 
-To declare an optional requirement, you need to add the *'optional'* attribute. To avoid `null` pointer exception, iPOJO injects a `Nullable` object in the field when no service provider is available. The *nullable* object implements the service interface, but does nothing. Moreover, it is possible to set a *default-implementation* for the service. A default-implementation is a class implementing the service but used only when no others service providers are available. The default-implementation object will be injected instead of the *Nullable* objet. For further information [refer to the note about nullable object]().
+<p>}</p>
+<div class="codehilite"><pre>For this component, equivalent XML metadata could be:
+{code:xml}
+<span class="nt">&lt;component</span> <span class="na">classname=</span><span class="s">&quot;...HelloConsumer&quot;</span><span class="nt">&gt;</span>
+    <span class="nt">&lt;requires</span> <span class="na">field=</span><span class="s">&quot;m_hello&quot;</span> <span class="na">optional=</span><span class="s">&quot;true&quot;</span><span class="nt">/&gt;</span>
+    ...
+<span class="nt">&lt;/component&gt;</span>
+</pre></div>
 
-#### Optional Dependency with callbacks invocation
 
-{code:java}
+<p>To declare an optional requirement, you need to add the <em>'optional'</em> attribute. To avoid <code>null</code> pointer exception, iPOJO injects a <code>Nullable</code> object in the field when no service provider is available. The <em>nullable</em> object implements the service interface, but does nothing. Moreover, it is possible to set a <em>default-implementation</em> for the service. A default-implementation is a class implementing the service but used only when no others service providers are available. The default-implementation object will be injected instead of the <em>Nullable</em> objet. For further information <a href="">refer to the note about nullable object</a>.</p>
+<h4 id="optional-dependency-with-callbacks-invocation">Optional Dependency with callbacks invocation</h4>
+<p>{code:java}
 @Component
 public class HelloConsumer {
-     private Hello m_hello;
-
-     @Bind(optional=true)
-     public void bindHello(Hello h) { m_hello = h; }
-
-     @Unbind
-     public void unbindHello() { m_hello = null; }
-
-     public doSomething() { 
-          if(m_hello != null) { // Must be checked
-              System.out.println(m_hello.getMesage()); 
-          }
-    }
-}
-
-    For this component, XML metadata could be:
-    {code:xml}
-    <component classname="...HelloConsumer">
-    <requires optional="true">
-        <callback type="bind" method="bindHello">
-        <callback type="unbind" method="unbindHello">
-    </requires>
-    ...
-    </component>
-
-As for field requirement, the dependency metadata needs to contain the optional attribute. iPOJO invokes the method only when a 'real' service is available, so you need to test if `m_hello` is `null` before to use it.
-
-### Aggregate & Optional Requirement
-
-A dependency can be both aggregate and optional.
-
-#### Aggregate & Optional Dependency with field injection
-
-{code:java}
+     private Hello m_hello;</p>
+<div class="codehilite"><pre> <span class="nv">@Bind</span><span class="p">(</span><span class="n">optional</span><span class="o">=</span><span class="n">true</span><span class="p">)</span>
+ <span class="n">public</span> <span class="n">void</span> <span class="n">bindHello</span><span class="p">(</span><span class="n">Hello</span> <span class="n">h</span><span class="p">)</span> <span class="p">{</span> <span class="n">m_hello</span> <span class="o">=</span> <span class="n">h</span><span class="p">;</span> <span class="p">}</span>
+
+ <span class="nv">@Unbind</span>
+ <span class="n">public</span> <span class="n">void</span> <span class="n">unbindHello</span><span class="p">()</span> <span class="p">{</span> <span class="n">m_hello</span> <span class="o">=</span> <span class="n">null</span><span class="p">;</span> <span class="p">}</span>
+
+ <span class="n">public</span> <span class="n">doSomething</span><span class="p">()</span> <span class="p">{</span> 
+      <span class="k">if</span><span class="p">(</span><span class="n">m_hello</span> <span class="o">!=</span> <span class="n">null</span><span class="p">)</span> <span class="p">{</span> <span class="sr">//</span> <span class="n">Must</span> <span class="n">be</span> <span class="n">checked</span>
+          <span class="n">System</span><span class="o">.</span><span class="n">out</span><span class="o">.</span><span class="n">println</span><span class="p">(</span><span class="n">m_hello</span><span class="o">.</span><span class="n">getMesage</span><span class="p">());</span> 
+      <span class="p">}</span>
+<span class="p">}</span>
+</pre></div>
+
+
+<p>}</p>
+<div class="codehilite"><pre>For this component, XML metadata could be:
+{code:xml}
+<span class="nt">&lt;component</span> <span class="na">classname=</span><span class="s">&quot;...HelloConsumer&quot;</span><span class="nt">&gt;</span>
+<span class="nt">&lt;requires</span> <span class="na">optional=</span><span class="s">&quot;true&quot;</span><span class="nt">&gt;</span>
+    <span class="nt">&lt;callback</span> <span class="na">type=</span><span class="s">&quot;bind&quot;</span> <span class="na">method=</span><span class="s">&quot;bindHello&quot;</span><span class="nt">&gt;</span>
+    <span class="nt">&lt;callback</span> <span class="na">type=</span><span class="s">&quot;unbind&quot;</span> <span class="na">method=</span><span class="s">&quot;unbindHello&quot;</span><span class="nt">&gt;</span>
+<span class="nt">&lt;/requires&gt;</span>
+...
+<span class="nt">&lt;/component&gt;</span>
+</pre></div>
+
+
+<p>As for field requirement, the dependency metadata needs to contain the optional attribute. iPOJO invokes the method only when a 'real' service is available, so you need to test if <code>m_hello</code> is <code>null</code> before to use it.</p>
+<h3 id="aggregate-optional-requirement">Aggregate &amp; Optional Requirement</h3>
+<p>A dependency can be both aggregate and optional.</p>
+<h4 id="aggregate-optional-dependency-with-field-injection">Aggregate &amp; Optional Dependency with field injection</h4>
+<p>{code:java}
 @Component
 public class HelloConsumer {
      @Requires(optional=true)
-     private Hello m_hellos[]();
-
-     public doSomething() {
-           for(Hello h : m_hellos) { 
-             System.out.println(h.getMessage());
-           }
-     }
-}
-
-    For this component, XML metadata could be:
-    {code:xml}
-    <component classname="...HelloConsumer">
-    <requires field="m_hellos" optional="true"/>
-    ...
-    </component>
-
-To declare an optional & aggregate field requirement you need to write the optional attribute in the dependency metadata and to point on a field array. If no service available, iPOJO injects an empty array.
-
-#### Aggregate & Optional Requirement with callbacks
-
-{code:java}
+     private Hello m_hellos<a href=""></a>;</p>
+<div class="codehilite"><pre> <span class="n">public</span> <span class="n">doSomething</span><span class="p">()</span> <span class="p">{</span>
+       <span class="k">for</span><span class="p">(</span><span class="n">Hello</span> <span class="n">h</span> <span class="p">:</span> <span class="n">m_hellos</span><span class="p">)</span> <span class="p">{</span> 
+         <span class="n">System</span><span class="o">.</span><span class="n">out</span><span class="o">.</span><span class="n">println</span><span class="p">(</span><span class="n">h</span><span class="o">.</span><span class="n">getMessage</span><span class="p">());</span>
+       <span class="p">}</span>
+ <span class="p">}</span>
+</pre></div>
+
+
+<p>}</p>
+<div class="codehilite"><pre>For this component, XML metadata could be:
+{code:xml}
+<span class="nt">&lt;component</span> <span class="na">classname=</span><span class="s">&quot;...HelloConsumer&quot;</span><span class="nt">&gt;</span>
+<span class="nt">&lt;requires</span> <span class="na">field=</span><span class="s">&quot;m_hellos&quot;</span> <span class="na">optional=</span><span class="s">&quot;true&quot;</span><span class="nt">/&gt;</span>
+...
+<span class="nt">&lt;/component&gt;</span>
+</pre></div>
+
+
+<p>To declare an optional &amp; aggregate field requirement you need to write the optional attribute in the dependency metadata and to point on a field array. If no service available, iPOJO injects an empty array.</p>
+<h4 id="aggregate-optional-requirement-with-callbacks">Aggregate &amp; Optional Requirement with callbacks</h4>
+<p>{code:java}
 @Compoent
-public class HelloConsumer {
-
-     private List m_hellos<Hello> = new ArrayList<Hello>();
-
-     @Bind(aggregate=true, optional=true)
-     private void bindHello(Hello h) { m_hellos.add(h); }
-
-     @Unbind
-     private void unbindHello(Hello h) { m_hellos.remove(h); }
-
-     public synchronized doSomething() {
-               for(Hello h : m_hellos) { 
-                  System.out.println(h.getMessage());
-               }
-     }
-}
-
-    For this component, XML metadata could be:
-    {code:xml}
-    <requires aggregate="true" optional="true">
-         <callback type="bind" method="bindHello">
-         <callback type="unbind" method="unbindHello">
-    </requires>
-
-In this case, you need to add the *'aggregate'*attribute and the *'optional'*attribute. The `bindHello` and `unbindHello` will be called each time a Hello service appears or disappears. These bind / unbind methods are not called when binding / unbinding a Nullable object (when both field and method are used).
-
-### Filtered Requirement
-
-A filtered dependency applies an LDAP filter on service provider. iPOJO reuses OSGi LDAP filter ability. The following metadata illustrates how to use filters:
-
-    @Requires(filter="(language=fr)")
-    private String DictionaryService dict;
-
-    <requires filter="(language=fr)" field="dict"/>
-
-To add a filter, just add a 'filter' attribute in your dependency containing the LDAP filter. iPOJO will select only provider matching with this filter.
-
-When using a filter, you can also use the `modified` callback invoked when a matching service is *modified* but still matches the filter:
-
-    @Component
-    public class MyComponent {
-
-        @Bind(filter="(langage=en)")
-        public void bindHDictionary(DictionaryService svc) { ... }
-
-        @Unbind
-        public void unbindDictionary() { ...}
-
-        @Modified
-        public void modifiedDictionary() { ... }
-
-    }
-
-Moreover, filters can be customized instance by instance. It is possible to specialize / change / add the filter of a component in the instance description. It is useful when you want to create different instances of the same component, with different filter. To achieve this customization, you have to identify your dependency with the 'id' attribute. Then, you can adapt the filter of the dependency in the instance description by using the property "requires.filters". In this property you can specify each dependency identified by its id and the new value of the filter.
-
-    <component 
-       className="org.apache.felix.ipojo.example.FilteredDependency">
-        <requires field="m_foo" fiter="(foo.property=FOO)" id="id1">
-            <callback type="bind" method="bind"/>
-            <callback type="unbind" method="unbind"/>
-        </requires>
-    </component>
-
-    <instance name="FOO1" component="FOO"/>
-
-    <instance name="FOO2" component="FOO">
-        <property name="requires.filters">
-            <property name="id1" value="(foo.property=BAR)"/>
-        </property>
-    </instance>
-
-    <instance name="FOO3" component="FOO">
-        <property name="requires.filters">
-            <property name="id1" value="(foo.property=BAZ)"/>
-        </property>
-    </instance>
-
-The component type declares a service dependency with the 'id1' id. This dependency has no filter by default. The first instance is just an instance of the FOO component type and does not modify the dependency. The second one adds a filter to the declared dependency to target providers with foo.property = BAR. The last one adds another filter to the declared dependency. By using instance filter customization, it is possible to create complex applications where you avoid binding problems by filtering dependencies instance by instance.
-
-### Targeting a specific provider
-A service dependency can choose a specific provider. To achieve this, add a 'from' attribute in your requirement description such as in:
-
-    @Requires(from="MyHelloProvider")
-    private Hello m_hello;
-
-or in XML:
-
-    <requires from="MyHelloProvider" field="m_hello"/>
-
-iPOJO maps the `from` attribute to a specific filter : '|(instance.name=MyHelloProvider)(service.pid=MyHelloProvider)'. Then the dependency can only be fulfilled by a service matching this filter.
-
-Moreover, from attributes can be customized instance by instance. It is possible to specialize / change / add a 'from' attribute of a component in the instance configuration. It is useful when you want to create different instances of the same component, with different 'from' clauses. To do it, you have to identify your dependency with an 'id' attribute. Then, you can adapt the 'from' of the dependency in the instance configuration by using the property "requires.from". In this property you can specify each dependency identified by its id and the 'from' value.
-
-    <component 
-       className="org.apache.felix.ipojo.example.FilteredDependency"
-       name="FOO">
-        <requires field="m_foo" id="id1">
-            <callback type="bind" method="bind"/>
-            <callback type="unbind" method="unbind"/>
-        </requires>
-    </component>
+public class HelloConsumer {</p>
+<div class="codehilite"><pre> <span class="n">private</span> <span class="n">List</span> <span class="n">m_hellos</span><span class="sr">&lt;Hello&gt;</span> <span class="o">=</span> <span class="k">new</span> <span class="n">ArrayList</span><span class="sr">&lt;Hello&gt;</span><span class="p">();</span>
 
-    <instance name="FOO1" component="FOO"/>
+ <span class="nv">@Bind</span><span class="p">(</span><span class="n">aggregate</span><span class="o">=</span><span class="n">true</span><span class="p">,</span> <span class="n">optional</span><span class="o">=</span><span class="n">true</span><span class="p">)</span>
+ <span class="n">private</span> <span class="n">void</span> <span class="n">bindHello</span><span class="p">(</span><span class="n">Hello</span> <span class="n">h</span><span class="p">)</span> <span class="p">{</span> <span class="n">m_hellos</span><span class="o">.</span><span class="n">add</span><span class="p">(</span><span class="n">h</span><span class="p">);</span> <span class="p">}</span>
 
-    <instance name="FOO2" component="FOO">
-        <property name="requires.from">
-            <property name="id1" value="myprovider"/>
-        </property>
-    </instance>
+ <span class="nv">@Unbind</span>
+ <span class="n">private</span> <span class="n">void</span> <span class="n">unbindHello</span><span class="p">(</span><span class="n">Hello</span> <span class="n">h</span><span class="p">)</span> <span class="p">{</span> <span class="n">m_hellos</span><span class="o">.</span><span class="n">remove</span><span class="p">(</span><span class="n">h</span><span class="p">);</span> <span class="p">}</span>
 
-    <instance name="FOO3" component="FOO">
-        <property name="requires.from">
-            <property name="id1" value="myotherprovider"/>
-        </property>
-    </instance>
-
-The FOO component type declares a service dependency with the 'id1' id. This dependency has no 'from' attribute by default. The first instance is just an instance of the FOO component type and does not modify the dependency. The second one adds a 'from' attribute to the declared dependency to target the 'myprovider' provider. The last one adds another 'from' clause to the declared dependency.
-
-## Binding Policies
-
-Three binding policies are supported inside iPOJO.
-* Dynamic policy (default): the binding are managed      dynamically. At each injection, the same provider is injected if the      provider is always available. Else a new one is chosen. For aggregate      dependency, the array order does not change; new providers are placed at      the end of the array.
-* Static policy: the binding is static. So, once      bound a provider cannot disappear. If it disappears, the instance is      invalidated and cannot be revalidated without stopping and restarting the      instance.
-* Dynamic-priority policy: the binding is managed      dynamically but the injected provider is selected by using a ranking      policy. Two injections can return two different providers, is a new      provider is 'better' than the previous one, despite the first one is always      available. For aggregate dependency, the array is sorted.
-
-A static binding is declared as following:
-
-    @Requires(policy="static")
-    private Hello[] m_hellos;
-
-or
-
-    <requires field="m_hellos" policy="static"/>
-
-A dynamic-priority binding is declared as following:
-
-    @Requires(policy="dynamic-priority")
-    private Hello[] m_hellos;
-
-or
-
-    <requires field="m_hellos" policy="dynamic-priority"/>
-
-By default, the dynamic-priority policy uses the OSGi service ranking policy. However, it is possible to customize the policy by adding the '*comparator*' attribute. This attribute indicates the class name of a class implementing the `java.util.Comparator` interface. iPOJO creates an instance of your comparator and uses it to sort service references (so your customized comparator needs to be able to sort OSGi Service Reference).
-
-    @Requires(policy="dynamic-priority", comparator=MyComparator.class)
-    private Hello[] m_hellos;
-
-or
-
-    <requires field="m_hellos" policy="dynamic-priority" comparator="great.MyComparator"/>
-
-## Note about nullable object & default-implementation
-
-The instance implementation can use an optional dependency without any checking. Indeed, when an instance declares an optional dependency using field injection, iPOJO create on the fly a Nullable class implementing the service specification but doing nothing (mock object). Therefore, iPOJO cannot return a service to the instance, for an optional dependency, it returns a nullable object.
-
-A nullable object returns:
-* Null when the method returns an object
-* 0 when the method returns an int, log, byte, short, char, float or a double
-* False when the method return a boolean
-
-You can check if the returned object is a nullable object with the test: *"myservice instanceof Nullable"*.
-
-You can disable the Nullable pattern too (activated by default). In this case, iPOJO injects `null` instead of a *Nullable* object. So, you can just test if your field is equals to *null* to check if the service is available. To disable the Nullable pattern, you need to add the 'nullable="false"' attribute in your service dependency description as follows:
-
-    @Requires(optional=true, nullable=false)
-    private LogService m_log;
-
-or
-
-     <requires field="m_log" optional="true" nullable="false"/>
-
-However, you can also indicate a *default-implementation* for your optional service. In this case, if no providers are found, iPOJO creates an instance of the default-implementation and injects it. The default-implementation attribute describes the class name of your implementation. The given class *MUST* implement the required service interface.
-
-For example, the following component uses a default implementation for a Log Service dependency:
-
-    @Requires(optional=true, default-implementation=MyLogService.class)
-    private LogService m_log;
-
-or
-
-    <requires field="m_log" optional="true" 
-        default-implementation=
-           "org.apache.felix.ipojo.example.default.MyLogService"/>
-
-If the log service is not available, iPOJO creates an object of the 'org.apache.felix.ipojo.example.default.MyLogService' class. This object is injected instead of a Nullable object. For instance, the default implementation can print messages on the System.err stream. The nullable object does no display anything.
-
-## Note about Callbacks
-Dependency manages two type of callback: bind and unbind. A callback with a type "bind" is called each type that a service provider arrives and the binding is necessary. According to the cardinality of the dependency it means:
-* Simple dependency : at the firs binding and at      each rebinding to another service provider
-* Aggregate dependencies: each time that a service      provider arrives
-
-An unbind callback is called each time that a *used* service provider goes away. For a simple dependency this method is called each time that the used service provider goes away. For a multiple dependency this method is called each time that a service provider goes away.
-
-The method can receive in argument the service object or the service reference (in order to obtain service properties). The bind methods are delayed since a POJO object is created.
-
-## Proxies
-Since iPOJO 1.6, iPOJO injects proxy objects. Those proxies are by default smart proxies and are design to be lightweight:
-* for scalar requirement : the service object is a proxy
-* for aggregate dependencies : iPOJO injects a smart collections
-
-The goal of the proxies is to hide the dynamism and more particularly the dynamism. So, you can gives a service dependency to another object, using the service object still supports the dynamism. For collections, you can iterate over the collection without managing the potential departures and arrivals of services. The proxy also manage that the component class and the delegate objects shared the same services is they are accessed in the same Thread.
-
-By default iPOJO injects proxy except for arrays. Moreover, it is possible to disable the proxy injection by adding `proxy=false` to the `requires` element (or to the `@Requires` and `@Bind` annotations). It is also possible to inject dynamic proxies (if the platform does not support dynamically generated classes). To enable dynamic proxies, set the system or bundle property `ipojo.proxy.type` to `dynamic-proxy`. You can also disable completely the proxy injection by setting the system property `ipojo.proxy` to `disabled`.
-
-## Note on service interface discovery
-
-The `specification` attribute is generally optional except when iPOJO cannot discover the type of the service. iPOJO cannot infer the type when the dependency has no field and callbacks do not receive the service object in parameter. In this case, you must the service specification (i.e. interface).
+ <span class="n">public</span> <span class="n">synchronized</span> <span class="n">doSomething</span><span class="p">()</span> <span class="p">{</span>
+           <span class="k">for</span><span class="p">(</span><span class="n">Hello</span> <span class="n">h</span> <span class="p">:</span> <span class="n">m_hellos</span><span class="p">)</span> <span class="p">{</span> 
+              <span class="n">System</span><span class="o">.</span><span class="n">out</span><span class="o">.</span><span class="n">println</span><span class="p">(</span><span class="n">h</span><span class="o">.</span><span class="n">getMessage</span><span class="p">());</span>
+           <span class="p">}</span>
+ <span class="p">}</span>
+</pre></div>
+
+
+<p>}</p>
+<div class="codehilite"><pre>For this component, XML metadata could be:
+{code:xml}
+<span class="nt">&lt;requires</span> <span class="na">aggregate=</span><span class="s">&quot;true&quot;</span> <span class="na">optional=</span><span class="s">&quot;true&quot;</span><span class="nt">&gt;</span>
+     <span class="nt">&lt;callback</span> <span class="na">type=</span><span class="s">&quot;bind&quot;</span> <span class="na">method=</span><span class="s">&quot;bindHello&quot;</span><span class="nt">&gt;</span>
+     <span class="nt">&lt;callback</span> <span class="na">type=</span><span class="s">&quot;unbind&quot;</span> <span class="na">method=</span><span class="s">&quot;unbindHello&quot;</span><span class="nt">&gt;</span>
+<span class="nt">&lt;/requires&gt;</span>
+</pre></div>
+
+
+<p>In this case, you need to add the <em>'aggregate'</em>attribute and the <em>'optional'</em>attribute. The <code>bindHello</code> and <code>unbindHello</code> will be called each time a Hello service appears or disappears. These bind / unbind methods are not called when binding / unbinding a Nullable object (when both field and method are used).</p>
+<h3 id="filtered-requirement">Filtered Requirement</h3>
+<p>A filtered dependency applies an LDAP filter on service provider. iPOJO reuses OSGi LDAP filter ability. The following metadata illustrates how to use filters:</p>
+<div class="codehilite"><pre><span class="nv">@Requires</span><span class="p">(</span><span class="n">filter</span><span class="o">=</span><span class="s">&quot;(language=fr)&quot;</span><span class="p">)</span>
+<span class="n">private</span> <span class="n">String</span> <span class="n">DictionaryService</span> <span class="n">dict</span><span class="p">;</span>
+
+<span class="o">&lt;</span><span class="n">requires</span> <span class="n">filter</span><span class="o">=</span><span class="s">&quot;(language=fr)&quot;</span> <span class="n">field</span><span class="o">=</span><span class="s">&quot;dict&quot;</span><span class="o">/&gt;</span>
+</pre></div>
+
+
+<p>To add a filter, just add a 'filter' attribute in your dependency containing the LDAP filter. iPOJO will select only provider matching with this filter.</p>
+<p>When using a filter, you can also use the <code>modified</code> callback invoked when a matching service is <em>modified</em> but still matches the filter:</p>
+<div class="codehilite"><pre><span class="nv">@Component</span>
+<span class="n">public</span> <span class="n">class</span> <span class="n">MyComponent</span> <span class="p">{</span>
+
+    <span class="nv">@Bind</span><span class="p">(</span><span class="n">filter</span><span class="o">=</span><span class="s">&quot;(langage=en)&quot;</span><span class="p">)</span>
+    <span class="n">public</span> <span class="n">void</span> <span class="n">bindHDictionary</span><span class="p">(</span><span class="n">DictionaryService</span> <span class="n">svc</span><span class="p">)</span> <span class="p">{</span> <span class="o">...</span> <span class="p">}</span>
+
+    <span class="nv">@Unbind</span>
+    <span class="n">public</span> <span class="n">void</span> <span class="n">unbindDictionary</span><span class="p">()</span> <span class="p">{</span> <span class="o">...</span><span class="p">}</span>
+
+    <span class="nv">@Modified</span>
+    <span class="n">public</span> <span class="n">void</span> <span class="n">modifiedDictionary</span><span class="p">()</span> <span class="p">{</span> <span class="o">...</span> <span class="p">}</span>
+
+<span class="p">}</span>
+</pre></div>
+
+
+<p>Moreover, filters can be customized instance by instance. It is possible to specialize / change / add the filter of a component in the instance description. It is useful when you want to create different instances of the same component, with different filter. To achieve this customization, you have to identify your dependency with the 'id' attribute. Then, you can adapt the filter of the dependency in the instance description by using the property "requires.filters". In this property you can specify each dependency identified by its id and the new value of the filter.</p>
+<div class="codehilite"><pre><span class="nt">&lt;component</span> 
+   <span class="na">className=</span><span class="s">&quot;org.apache.felix.ipojo.example.FilteredDependency&quot;</span><span class="nt">&gt;</span>
+    <span class="nt">&lt;requires</span> <span class="na">field=</span><span class="s">&quot;m_foo&quot;</span> <span class="na">fiter=</span><span class="s">&quot;(foo.property=FOO)&quot;</span> <span class="na">id=</span><span class="s">&quot;id1&quot;</span><span class="nt">&gt;</span>
+        <span class="nt">&lt;callback</span> <span class="na">type=</span><span class="s">&quot;bind&quot;</span> <span class="na">method=</span><span class="s">&quot;bind&quot;</span><span class="nt">/&gt;</span>
+        <span class="nt">&lt;callback</span> <span class="na">type=</span><span class="s">&quot;unbind&quot;</span> <span class="na">method=</span><span class="s">&quot;unbind&quot;</span><span class="nt">/&gt;</span>
+    <span class="nt">&lt;/requires&gt;</span>
+<span class="nt">&lt;/component&gt;</span>
+
+<span class="nt">&lt;instance</span> <span class="na">name=</span><span class="s">&quot;FOO1&quot;</span> <span class="na">component=</span><span class="s">&quot;FOO&quot;</span><span class="nt">/&gt;</span>
+
+<span class="nt">&lt;instance</span> <span class="na">name=</span><span class="s">&quot;FOO2&quot;</span> <span class="na">component=</span><span class="s">&quot;FOO&quot;</span><span class="nt">&gt;</span>
+    <span class="nt">&lt;property</span> <span class="na">name=</span><span class="s">&quot;requires.filters&quot;</span><span class="nt">&gt;</span>
+        <span class="nt">&lt;property</span> <span class="na">name=</span><span class="s">&quot;id1&quot;</span> <span class="na">value=</span><span class="s">&quot;(foo.property=BAR)&quot;</span><span class="nt">/&gt;</span>
+    <span class="nt">&lt;/property&gt;</span>
+<span class="nt">&lt;/instance&gt;</span>
+
+<span class="nt">&lt;instance</span> <span class="na">name=</span><span class="s">&quot;FOO3&quot;</span> <span class="na">component=</span><span class="s">&quot;FOO&quot;</span><span class="nt">&gt;</span>
+    <span class="nt">&lt;property</span> <span class="na">name=</span><span class="s">&quot;requires.filters&quot;</span><span class="nt">&gt;</span>
+        <span class="nt">&lt;property</span> <span class="na">name=</span><span class="s">&quot;id1&quot;</span> <span class="na">value=</span><span class="s">&quot;(foo.property=BAZ)&quot;</span><span class="nt">/&gt;</span>
+    <span class="nt">&lt;/property&gt;</span>
+<span class="nt">&lt;/instance&gt;</span>
+</pre></div>
+
+
+<p>The component type declares a service dependency with the 'id1' id. This dependency has no filter by default. The first instance is just an instance of the FOO component type and does not modify the dependency. The second one adds a filter to the declared dependency to target providers with foo.property = BAR. The last one adds another filter to the declared dependency. By using instance filter customization, it is possible to create complex applications where you avoid binding problems by filtering dependencies instance by instance.</p>
+<h3 id="targeting-a-specific-provider">Targeting a specific provider</h3>
+<p>A service dependency can choose a specific provider. To achieve this, add a 'from' attribute in your requirement description such as in:</p>
+<div class="codehilite"><pre><span class="nv">@Requires</span><span class="p">(</span><span class="n">from</span><span class="o">=</span><span class="s">&quot;MyHelloProvider&quot;</span><span class="p">)</span>
+<span class="n">private</span> <span class="n">Hello</span> <span class="n">m_hello</span><span class="p">;</span>
+</pre></div>
+
+
+<p>or in XML:</p>
+<div class="codehilite"><pre><span class="o">&lt;</span><span class="n">requires</span> <span class="n">from</span><span class="o">=</span><span class="s">&quot;MyHelloProvider&quot;</span> <span class="n">field</span><span class="o">=</span><span class="s">&quot;m_hello&quot;</span><span class="o">/&gt;</span>
+</pre></div>
+
+
+<p>iPOJO maps the <code>from</code> attribute to a specific filter : '|(instance.name=MyHelloProvider)(service.pid=MyHelloProvider)'. Then the dependency can only be fulfilled by a service matching this filter.</p>
+<p>Moreover, from attributes can be customized instance by instance. It is possible to specialize / change / add a 'from' attribute of a component in the instance configuration. It is useful when you want to create different instances of the same component, with different 'from' clauses. To do it, you have to identify your dependency with an 'id' attribute. Then, you can adapt the 'from' of the dependency in the instance configuration by using the property "requires.from". In this property you can specify each dependency identified by its id and the 'from' value.</p>
+<div class="codehilite"><pre><span class="nt">&lt;component</span> 
+   <span class="na">className=</span><span class="s">&quot;org.apache.felix.ipojo.example.FilteredDependency&quot;</span>
+   <span class="na">name=</span><span class="s">&quot;FOO&quot;</span><span class="nt">&gt;</span>
+    <span class="nt">&lt;requires</span> <span class="na">field=</span><span class="s">&quot;m_foo&quot;</span> <span class="na">id=</span><span class="s">&quot;id1&quot;</span><span class="nt">&gt;</span>
+        <span class="nt">&lt;callback</span> <span class="na">type=</span><span class="s">&quot;bind&quot;</span> <span class="na">method=</span><span class="s">&quot;bind&quot;</span><span class="nt">/&gt;</span>
+        <span class="nt">&lt;callback</span> <span class="na">type=</span><span class="s">&quot;unbind&quot;</span> <span class="na">method=</span><span class="s">&quot;unbind&quot;</span><span class="nt">/&gt;</span>
+    <span class="nt">&lt;/requires&gt;</span>
+<span class="nt">&lt;/component&gt;</span>
+
+<span class="nt">&lt;instance</span> <span class="na">name=</span><span class="s">&quot;FOO1&quot;</span> <span class="na">component=</span><span class="s">&quot;FOO&quot;</span><span class="nt">/&gt;</span>
+
+<span class="nt">&lt;instance</span> <span class="na">name=</span><span class="s">&quot;FOO2&quot;</span> <span class="na">component=</span><span class="s">&quot;FOO&quot;</span><span class="nt">&gt;</span>
+    <span class="nt">&lt;property</span> <span class="na">name=</span><span class="s">&quot;requires.from&quot;</span><span class="nt">&gt;</span>
+        <span class="nt">&lt;property</span> <span class="na">name=</span><span class="s">&quot;id1&quot;</span> <span class="na">value=</span><span class="s">&quot;myprovider&quot;</span><span class="nt">/&gt;</span>
+    <span class="nt">&lt;/property&gt;</span>
+<span class="nt">&lt;/instance&gt;</span>
+
+<span class="nt">&lt;instance</span> <span class="na">name=</span><span class="s">&quot;FOO3&quot;</span> <span class="na">component=</span><span class="s">&quot;FOO&quot;</span><span class="nt">&gt;</span>
+    <span class="nt">&lt;property</span> <span class="na">name=</span><span class="s">&quot;requires.from&quot;</span><span class="nt">&gt;</span>
+        <span class="nt">&lt;property</span> <span class="na">name=</span><span class="s">&quot;id1&quot;</span> <span class="na">value=</span><span class="s">&quot;myotherprovider&quot;</span><span class="nt">/&gt;</span>
+    <span class="nt">&lt;/property&gt;</span>
+<span class="nt">&lt;/instance&gt;</span>
+</pre></div>
+
+
+<p>The FOO component type declares a service dependency with the 'id1' id. This dependency has no 'from' attribute by default. The first instance is just an instance of the FOO component type and does not modify the dependency. The second one adds a 'from' attribute to the declared dependency to target the 'myprovider' provider. The last one adds another 'from' clause to the declared dependency.</p>
+<h2 id="binding-policies">Binding Policies</h2>
+<p>Three binding policies are supported inside iPOJO.
+<em> Dynamic policy (default): the binding are managed      dynamically. At each injection, the same provider is injected if the      provider is always available. Else a new one is chosen. For aggregate      dependency, the array order does not change; new providers are placed at      the end of the array.
+</em> Static policy: the binding is static. So, once      bound a provider cannot disappear. If it disappears, the instance is      invalidated and cannot be revalidated without stopping and restarting the      instance.
+* Dynamic-priority policy: the binding is managed      dynamically but the injected provider is selected by using a ranking      policy. Two injections can return two different providers, is a new      provider is 'better' than the previous one, despite the first one is always      available. For aggregate dependency, the array is sorted.</p>
+<p>A static binding is declared as following:</p>
+<div class="codehilite"><pre><span class="nv">@Requires</span><span class="p">(</span><span class="n">policy</span><span class="o">=</span><span class="s">&quot;static&quot;</span><span class="p">)</span>
+<span class="n">private</span> <span class="n">Hello</span><span class="o">[]</span> <span class="n">m_hellos</span><span class="p">;</span>
+</pre></div>
+
+
+<p>or</p>
+<div class="codehilite"><pre><span class="o">&lt;</span><span class="n">requires</span> <span class="n">field</span><span class="o">=</span><span class="s">&quot;m_hellos&quot;</span> <span class="n">policy</span><span class="o">=</span><span class="s">&quot;static&quot;</span><span class="o">/&gt;</span>
+</pre></div>
+
+
+<p>A dynamic-priority binding is declared as following:</p>
+<div class="codehilite"><pre><span class="nv">@Requires</span><span class="p">(</span><span class="n">policy</span><span class="o">=</span><span class="s">&quot;dynamic-priority&quot;</span><span class="p">)</span>
+<span class="n">private</span> <span class="n">Hello</span><span class="o">[]</span> <span class="n">m_hellos</span><span class="p">;</span>
+</pre></div>
+
+
+<p>or</p>
+<div class="codehilite"><pre><span class="o">&lt;</span><span class="n">requires</span> <span class="n">field</span><span class="o">=</span><span class="s">&quot;m_hellos&quot;</span> <span class="n">policy</span><span class="o">=</span><span class="s">&quot;dynamic-priority&quot;</span><span class="o">/&gt;</span>
+</pre></div>
+
+
+<p>By default, the dynamic-priority policy uses the OSGi service ranking policy. However, it is possible to customize the policy by adding the '<em>comparator</em>' attribute. This attribute indicates the class name of a class implementing the <code>java.util.Comparator</code> interface. iPOJO creates an instance of your comparator and uses it to sort service references (so your customized comparator needs to be able to sort OSGi Service Reference).</p>
+<div class="codehilite"><pre><span class="nv">@Requires</span><span class="p">(</span><span class="n">policy</span><span class="o">=</span><span class="s">&quot;dynamic-priority&quot;</span><span class="p">,</span> <span class="n">comparator</span><span class="o">=</span><span class="n">MyComparator</span><span class="o">.</span><span class="n">class</span><span class="p">)</span>
+<span class="n">private</span> <span class="n">Hello</span><span class="o">[]</span> <span class="n">m_hellos</span><span class="p">;</span>
+</pre></div>
+
+
+<p>or</p>
+<div class="codehilite"><pre><span class="o">&lt;</span><span class="n">requires</span> <span class="n">field</span><span class="o">=</span><span class="s">&quot;m_hellos&quot;</span> <span class="n">policy</span><span class="o">=</span><span class="s">&quot;dynamic-priority&quot;</span> <span class="n">comparator</span><span class="o">=</span><span class="s">&quot;great.MyComparator&quot;</span><span class="o">/&gt;</span>
+</pre></div>
+
+
+<h2 id="note-about-nullable-object-default-implementation">Note about nullable object &amp; default-implementation</h2>
+<p>The instance implementation can use an optional dependency without any checking. Indeed, when an instance declares an optional dependency using field injection, iPOJO create on the fly a Nullable class implementing the service specification but doing nothing (mock object). Therefore, iPOJO cannot return a service to the instance, for an optional dependency, it returns a nullable object.</p>
+<p>A nullable object returns:
+<em> Null when the method returns an object
+</em> 0 when the method returns an int, log, byte, short, char, float or a double
+* False when the method return a boolean</p>
+<p>You can check if the returned object is a nullable object with the test: <em>"myservice instanceof Nullable"</em>.</p>
+<p>You can disable the Nullable pattern too (activated by default). In this case, iPOJO injects <code>null</code> instead of a <em>Nullable</em> object. So, you can just test if your field is equals to <em>null</em> to check if the service is available. To disable the Nullable pattern, you need to add the 'nullable="false"' attribute in your service dependency description as follows:</p>
+<div class="codehilite"><pre><span class="nv">@Requires</span><span class="p">(</span><span class="n">optional</span><span class="o">=</span><span class="n">true</span><span class="p">,</span> <span class="n">nullable</span><span class="o">=</span><span class="n">false</span><span class="p">)</span>
+<span class="n">private</span> <span class="n">LogService</span> <span class="n">m_log</span><span class="p">;</span>
+</pre></div>
+
+
+<p>or</p>
+<div class="codehilite"><pre> <span class="o">&lt;</span><span class="n">requires</span> <span class="n">field</span><span class="o">=</span><span class="s">&quot;m_log&quot;</span> <span class="n">optional</span><span class="o">=</span><span class="s">&quot;true&quot;</span> <span class="n">nullable</span><span class="o">=</span><span class="s">&quot;false&quot;</span><span class="o">/&gt;</span>
+</pre></div>
+
+
+<p>However, you can also indicate a <em>default-implementation</em> for your optional service. In this case, if no providers are found, iPOJO creates an instance of the default-implementation and injects it. The default-implementation attribute describes the class name of your implementation. The given class <em>MUST</em> implement the required service interface.</p>
+<p>For example, the following component uses a default implementation for a Log Service dependency:</p>
+<div class="codehilite"><pre><span class="nv">@Requires</span><span class="p">(</span><span class="n">optional</span><span class="o">=</span><span class="n">true</span><span class="p">,</span> <span class="n">default</span><span class="o">-</span><span class="n">implementation</span><span class="o">=</span><span class="n">MyLogService</span><span class="o">.</span><span class="n">class</span><span class="p">)</span>

[... 57 lines stripped ...]


Mime
View raw message