svn commit: r859833 - in /websites/staging/felix/trunk/content: ./ documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/service-requirement-handler.html

[bu...@apache.org]

Author: buildbot
Date: Thu Apr 25 08:30:50 2013
New Revision: 859833

Log:
Staging update by buildbot for felix

Modified:
    websites/staging/felix/trunk/content/   (props changed)
    websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/service-requirement-handler.html

Propchange: websites/staging/felix/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Apr 25 08:30:50 2013
@@ -1 +1 @@
-1475667
+1475668

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 Thu Apr 25 08:30:50 2013
@@ -315,7 +315,7 @@
 
 
 <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>
+(<a href="#note-on-service-interface-discovery">See note on type discovery</a></p>
 <p>Using the <code>@Modified</code> callback is also quite simple:</p>
 <div class="codehilite"><pre><span class="nd">@Component</span>
 <span class="kd">public</span> <span class="kd">class</span> <span class="nc">HelloConsumer</span> <span class="o">{</span>
@@ -511,7 +511,7 @@ public class HelloConsumer {
 </pre></div>
 
 
-<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>
+<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="#note-about-nullable-object-default-implementation">refer to the note about nullable object</a>.</p>
 <h4 id="optional-dependency-with-callbacks-invocation">Optional Dependency with callbacks invocation</h4>
 <div class="codehilite"><pre><span class="nd">@Component</span>
 <span class="kd">public</span> <span class="kd">class</span> <span class="nc">HelloConsumer</span> <span class="o">{</span>
@@ -667,7 +667,7 @@ public class HelloConsumer {
 </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>iPOJO maps the <code>from</code> attribute to a specific filter : <code>|(instance.name=MyHelloProvider)(service.pid=MyHelloProvider)</code>. 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>
@@ -802,7 +802,7 @@ public class HelloConsumer {
                 may be trademarks or registered trademarks of their respective owners.
                 </div>
                 <div class="timestamp span3 offset2">
-                Rev. 1475667 by clement on Thu, 25 Apr 2013 08:24:33 +0000
+                Rev. 1475668 by clement on Thu, 25 Apr 2013 08:30:42 +0000
                 </div>
             </div>
         </footer>