You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@felix.apache.org by bu...@apache.org on 2013/02/13 10:20:59 UTC
svn commit: r850462 [2/2] - in /websites/staging/felix/trunk/content: ./
documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/
ipojo/site/
Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/ipojo-faq.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/ipojo-faq.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/ipojo-faq.html Wed Feb 13 09:20:58 2013
@@ -154,136 +154,151 @@
<div class="container">
<div class="content">
<h1 id="apache-felix-ipojo-faq">Apache Felix iPOJO FAQ</h1>
-<p>{div:class=toc}
-[TOC]
-{div}</p>
+<div class="toc">
+<ul>
+<li><a href="#apache-felix-ipojo-faq">Apache Felix iPOJO FAQ</a><ul>
+<li><a href="#injecting-the-bundle-context-in-a-pojo">Injecting the bundle context in a POJO</a></li>
+<li><a href="#accessing-services-inside-inner-and-anonymous-classes">Accessing services inside inner and anonymous classes</a></li>
+<li><a href="#using-a-different-version-of-the-manipulator-during-the-manipulation">Using a different version of the manipulator during the manipulation</a></li>
+<li><a href="#callbacks-order">Callbacks order.</a></li>
+<li><a href="#disabling-proxies-in-ipojo-16">Disabling proxies in iPOJO 1.6+</a></li>
+<li><a href="#use-dynamic-proxies-instead-of-smart-proxies">Use dynamic proxies instead of smart proxies</a></li>
+<li><a href="#can-i-use-ipojo-with-other-osgi-implementations">Can I use iPOJO with other OSGi implementations?</a></li>
+<li><a href="#detecting-optional-service-unavailability">Detecting optional service unavailability</a></li>
+<li><a href="#setting-the-ipojo-log-level">Setting the iPOJO log level</a></li>
+<li><a href="#installing-ipojo-in-service-mix-kernel">Installing iPOJO in Service Mix Kernel</a></li>
+<li><a href="#ipojo-and-file-install">iPOJO and File Install</a></li>
+<li><a href="#ipojo-handler-start-level">iPOJO handler start level</a></li>
+<li><a href="#why-does-my-bundle-import-unused-packages">Why does my bundle import unused packages?</a></li>
+<li><a href="#how-does-ipojo-compare-to-declarative-services-or-blueprint">How does iPOJO compare to Declarative Services or Blueprint?</a></li>
+</ul>
+</li>
+</ul>
+</div>
<h2 id="injecting-the-bundle-context-in-a-pojo">Injecting the bundle context in a POJO</h2>
-<p>It is sometimes useful to inject the bundle context in your POJO. Then, your POJO is able to deal with the OSGi environment as <em>regular</em> OSGi applications. It is possible to a POJO to get its <code>BundleContext</code>. A POJO can receive its bundle context as an argument of its constructor. The next code snippet shows an example:
-{code:java}
-public class ASimplePOJO{
- private BundleContext context;
- public ASimplePOJO(BundleContext bc) {
- context = bc;
- // do something...
- }}</p>
-<div class="codehilite"><pre><span class="n">As</span> <span class="n">you</span> <span class="n">see</span> <span class="n">on</span> <span class="n">the</span> <span class="n">previous</span> <span class="n">snippet</span><span class="p">,</span> <span class="n">the</span> <span class="n">bundle</span> <span class="n">context</span> <span class="n">is</span> <span class="n">injected</span> <span class="n">in</span> <span class="n">the</span> <span class="n">POJO</span><span class="o">.</span> <span class="n">Then</span> <span class="n">the</span> <span class="n">POJO</span> <span class="n">can</span> <span class="k">use</span> <span class="n">it</span> <span class="n">as</span> <span class="n">a</span> <span class="s">'normal'</span> <span class="n">bundle</span> <span class="n">context</span><span class="o">.</span> <span class="n">The</span> <span class="n">POJO</span> <span class="n">code</span> <span class="n">can:</span>
-<span class="o">*</span> <span class="n">load</span> <span class="n">classes</span>
-<span class="o">*</span> <span class="n">register</span> <span class="o">/</span> <span class="n">unregister</span> <span class="n">services</span>
-<span class="o">*</span> <span class="n">discover</span><span class="p">,</span> <span class="n">track</span> <span class="ow">and</span> <span class="k">use</span> <span class="n">services</span>
-
-<span class="n">However</span><span class="p">,</span> <span class="n">all</span> <span class="n">these</span> <span class="n">interactions</span> <span class="n">are</span> <span class="nb">no</span> <span class="n">more</span> <span class="n">managed</span> <span class="n">by</span> <span class="n">the</span> <span class="n">iPOJO</span> <span class="n">container</span><span class="o">.</span> <span class="n">So</span><span class="p">,</span> <span class="n">be</span> <span class="n">careful</span> <span class="n">to</span> <span class="n">manage</span> <span class="n">the</span> <span class="n">dynamism</span><span class="p">,</span> <span class="n">synchronization</span><span class="p">,</span> <span class="n">listeners</span><span class="o">...</span>
-
-<span class="n">h2</span><span class="o">.</span> <span class="n">Accessing</span> <span class="n">services</span> <span class="n">inside</span> <span class="n">inner</span> <span class="ow">and</span> <span class="n">anonymous</span> <span class="n">classes</span>
-
-<span class="n">An</span> <span class="n">inner</span> <span class="n">class</span> <span class="n">is</span> <span class="n">a</span> <span class="n">class</span> <span class="nb">defined</span> <span class="n">inside</span> <span class="n">another</span> <span class="n">class</span><span class="o">.</span> <span class="n">This</span> <span class="n">mechanism</span> <span class="n">is</span> <span class="n">useful</span> <span class="n">in</span> <span class="n">order</span> <span class="n">to</span> <span class="n">avoid</span> <span class="n">creating</span> <span class="n">a</span> <span class="n">bunch</span> <span class="n">of</span> <span class="n">small</span> <span class="n">files</span><span class="o">.</span> <span class="n">So</span><span class="p">,</span> <span class="n">it</span> <span class="n">is</span> <span class="n">common</span> <span class="n">when</span> <span class="n">creating</span> <span class="n">threads</span><span class="p">,</span> <span clas
s="n">Swing</span> <span class="n">listeners</span> <span class="o">...</span> <span class="n">Generally</span> <span class="n">speaking</span><span class="p">,</span> <span class="n">inner</span> <span class="n">classes</span> <span class="n">are</span> <span class="n">regular</span> <span class="n">classes</span> <span class="n">treated</span> <span class="n">as</span> <span class="n">separate</span> <span class="n">classes</span><span class="o">.</span> <span class="n">However</span> <span class="n">this</span> <span class="n">is</span> <span class="n">an</span> <span class="n">oversimplification</span><span class="o">.</span> <span class="n">Some</span> <span class="n">of</span> <span class="n">the</span> <span class="n">information</span> <span class="n">about</span> <span class="n">an</span> <span class="n">inner</span> <span class="n">class</span> <span class="n">is</span> <span class="ow">not</span> <span class="n">in</span> <span class="n">its</span> <span class="n"
>class</span> <span class="n">file</span><span class="o">.</span> <span class="n">See</span> <span class="n">section</span> <span class="mf">4.7.5</span> <span class="k">for</span> <span class="n">further</span> <span class="n">details:</span>
-<span class="p">[</span><span class="n">http:</span><span class="sr">//</span><span class="n">java</span><span class="o">.</span><span class="n">sun</span><span class="o">.</span><span class="n">com</span><span class="sr">/docs/</span><span class="n">books</span><span class="sr">/jvms/s</span><span class="n">econd_edition</span><span class="sr">/html/</span><span class="n">ClassFile</span><span class="o">.</span><span class="n">doc</span><span class="o">.</span><span class="n">html</span><span class="p">]</span>
-
-<span class="n">An</span> <span class="n">inner</span> <span class="n">class</span> <span class="n">can</span> <span class="n">access</span> <span class="n">fields</span> <span class="n">of</span> <span class="n">its</span> <span class="n">outer</span> <span class="n">class</span><span class="o">.</span> <span class="n">Since</span> <span class="n">the</span> <span class="n">iPOJO</span> <span class="mf">1.0.0</span> <span class="n">version</span><span class="p">,</span> <span class="n">fields</span> <span class="n">managed</span> <span class="n">by</span> <span class="n">iPOJO</span><span class="p">,</span> <span class="n">such</span> <span class="n">as</span> <span class="n">a</span> <span class="n">service</span> <span class="n">dependencies</span> <span class="ow">and</span> <span class="n">properties</span><span class="p">,</span> <span class="n">are</span> <span class="n">also</span> <span class="n">available</span> <span class="n">from</span> <span class="n">the</span
> <span class="n">inner</span> <span class="n">class</span><span class="o">.</span> <span class="n">Indeed</span><span class="p">,</span> <span class="n">iPOJO</span> <span class="n">manipulation</span> <span class="n">also</span> <span class="n">manipulates</span> <span class="n">inner</span> <span class="ow">and</span> <span class="n">nested</span> <span class="n">classes</span><span class="p">,</span> <span class="ow">and</span> <span class="n">accesses</span> <span class="n">to</span> <span class="n">outer</span> <span class="n">class</span> <span class="n">fields</span> <span class="n">are</span> <span class="n">correctly</span> <span class="n">managed</span><span class="o">.</span>
-
-<span class="n">h2</span><span class="o">.</span> <span class="n">Using</span> <span class="n">a</span> <span class="n">different</span> <span class="n">version</span> <span class="n">of</span> <span class="n">the</span> <span class="n">manipulator</span> <span class="n">during</span> <span class="n">the</span> <span class="n">manipulation</span>
-
-<span class="n">You</span> <span class="n">can</span> <span class="n">configure</span> <span class="n">the</span> <span class="n">version</span> <span class="n">of</span> <span class="n">the</span> <span class="n">manipulator</span> <span class="n">that</span> <span class="n">you</span> <span class="n">want</span> <span class="n">to</span> <span class="k">use</span> <span class="n">when</span> <span class="n">you</span><span class="err">'</span><span class="n">re</span> <span class="n">using</span> <span class="n">the</span> <span class="n">maven</span><span class="o">-</span><span class="n">ipojo</span><span class="o">-</span><span class="n">plugin</span> <span class="ow">or</span> <span class="n">the</span> <span class="n">iPOJO</span> <span class="n">ant</span> <span class="n">task</span><span class="o">.</span> <span class="n">This</span> <span class="n">allows</span> <span class="n">to</span> <span class="n">benefit</span> <span class="n">latest</span> <span class="
n">improvements</span><span class="o">.</span>
-
-<span class="n">For</span> <span class="n">Maven</span><span class="p">,</span> <span class="n">Just</span> <span class="n">declare</span> <span class="n">a</span> <span class="n">dependency</span> <span class="n">on</span> <span class="n">the</span> <span class="n">manipulator</span> <span class="n">that</span> <span class="n">you</span> <span class="n">want</span> <span class="n">to</span> <span class="k">use</span> <span class="n">in</span> <span class="n">the</span> <span class="n">maven</span><span class="o">-</span><span class="n">ipojo</span><span class="o">-</span><span class="n">plugin</span> <span class="n">plugin</span> <span class="n">section:</span>
-<span class="p">{</span><span class="n">code:xml</span><span class="o">|</span><span class="n">title</span><span class="o">=</span><span class="n">Maven</span><span class="p">}</span>
-<span class="sr"><plugin></span>
- <span class="sr"><groupId></span><span class="n">org</span><span class="o">.</span><span class="n">apache</span><span class="o">.</span><span class="n">felix</span><span class="sr"></groupId></span>
- <span class="sr"><artifactId></span><span class="n">maven</span><span class="o">-</span><span class="n">ipojo</span><span class="o">-</span><span class="n">plugin</span><span class="sr"></artifactId></span>
- <span class="sr"><executions></span>
- <span class="sr"><execution></span>
- <span class="sr"><goals></span>
- <span class="sr"><goal></span><span class="n">ipojo</span><span class="o">-</span><span class="n">bundle</span><span class="sr"></goal></span>
- <span class="sr"></goals></span>
- <span class="sr"></execution></span>
- <span class="sr"></executions></span>
- <span class="sr"><dependencies></span>
- <span class="sr"><dependency></span>
- <span class="sr"><groupId></span><span class="n">org</span><span class="o">.</span><span class="n">apache</span><span class="o">.</span><span class="n">felix</span><span class="sr"></groupId></span>
- <span class="sr"><artifactId></span><span class="n">org</span><span class="o">.</span><span class="n">apache</span><span class="o">.</span><span class="n">felix</span><span class="o">.</span><span class="n">ipojo</span><span class="o">.</span><span class="n">manipulator</span><span class="sr"></artifactId></span>
- <span class="sr"><version></span><span class="mf">1.6.2</span><span class="sr"></version></span>
- <span class="sr"></dependency></span>
- <span class="sr"></dependencies></span>
- <span class="sr"></plugin></span>
+<p>It is sometimes useful to inject the bundle context in your POJO. Then, your POJO is able to deal with the OSGi environment as <em>regular</em> OSGi applications. It is possible to a POJO to get its <code>BundleContext</code>. A POJO can receive its bundle context as an argument of its constructor. The next code snippet shows an example:</p>
+<div class="codehilite"><pre><span class="kd">public</span> <span class="kd">class</span> <span class="nc">ASimplePOJO</span><span class="o">{</span>
+ <span class="kd">private</span> <span class="n">BundleContext</span> <span class="n">context</span><span class="o">;</span>
+ <span class="kd">public</span> <span class="nf">ASimplePOJO</span><span class="o">(</span><span class="n">BundleContext</span> <span class="n">bc</span><span class="o">)</span> <span class="o">{</span>
+ <span class="n">context</span> <span class="o">=</span> <span class="n">bc</span><span class="o">;</span>
+ <span class="c1">// do something...</span>
+ <span class="o">}</span>
+<span class="o">}</span>
+</pre></div>
+
+
+<p>As you see on the previous snippet, the bundle context is injected in the POJO. Then the POJO can use it as a 'normal' bundle context. The POJO code can:</p>
+<ul>
+<li>load classes</li>
+<li>register / unregister services</li>
+<li>discover, track and use services</li>
+</ul>
+<p>However, all these interactions are no more managed by the iPOJO container. So, be careful to manage the dynamism, synchronization, listeners...</p>
+<h2 id="accessing-services-inside-inner-and-anonymous-classes">Accessing services inside inner and anonymous classes</h2>
+<p>An inner class is a class defined inside another class. This mechanism is useful in order to avoid creating a bunch of small files. So, it is common when creating threads, Swing listeners ... Generally speaking, inner classes are regular classes treated as separate classes. However this is an oversimplification. Some of the information about an inner class is not in its class file. See section 4.7.5 for further details on [http://java.sun.com/docs/books/jvms/second_edition/html/ClassFile.doc.html]</p>
+<p>An inner class can access fields of its outer class. Since the iPOJO 1.0.0 version, fields managed by iPOJO, such as a service dependencies and properties, are also available from the inner class. Indeed, iPOJO manipulation also manipulates inner and nested classes, and accesses to outer class fields are correctly managed.</p>
+<h2 id="using-a-different-version-of-the-manipulator-during-the-manipulation">Using a different version of the manipulator during the manipulation</h2>
+<p>You can configure the version of the manipulator that you want to use when you're using the maven-ipojo-plugin or the iPOJO ant task. This allows to benefit latest improvements.</p>
+<p>For Maven, Just declare a dependency on the manipulator that you want to use in the maven-ipojo-plugin plugin section:</p>
+<div class="codehilite"><pre><span class="nt"><plugin></span>
+ <span class="nt"><groupId></span>org.apache.felix<span class="nt"></groupId></span>
+ <span class="nt"><artifactId></span>maven-ipojo-plugin<span class="nt"></artifactId></span>
+ <span class="nt"><executions></span>
+ <span class="nt"><execution></span>
+ <span class="nt"><goals></span>
+ <span class="nt"><goal></span>ipojo-bundle<span class="nt"></goal></span>
+ <span class="nt"></goals></span>
+ <span class="nt"></execution></span>
+ <span class="nt"></executions></span>
+ <span class="nt"><dependencies></span>
+ <span class="nt"><dependency></span>
+ <span class="nt"><groupId></span>org.apache.felix<span class="nt"></groupId></span>
+ <span class="nt"><artifactId></span>org.apache.felix.ipojo.manipulator<span class="nt"></artifactId></span>
+ <span class="nt"><version></span>1.8.6<span class="nt"></version></span>
+ <span class="nt"></dependency></span>
+ <span class="nt"></dependencies></span>
+ <span class="nt"></plugin></span>
+</pre></div>
+
+
+<p>For Ant, just configure the classpath of the iPOJO ant task with the Manipulator that you want to use:</p>
+<div class="codehilite"><pre><span class="nt"><taskdef</span> <span class="na">name=</span><span class="s">"ipojo"</span>
+ <span class="na">classname=</span><span class="s">"org.apache.felix.ipojo.task.IPojoTask"</span>
+ <span class="na">classpath=</span><span class="s">"../ipojo/manipulator/org.apache.felix.ipojo.manipulator-1.7.0-SNAPSHOT.jar; lib/org.apache.felix.ipojo.ant-1.7.0-SNAPSHOT.jar;"</span> <span class="nt">/></span>
+ />
</pre></div>
-<p>For Ant, just configure the classpath of the iPOJO ant task with the Manipulator that you want to use:
-{code:xml|title=Ant}
-<taskdef name="ipojo"
- classname="org.apache.felix.ipojo.task.IPojoTask"
- classpath="../ipojo/manipulator/org.apache.felix.ipojo.manipulator-1.7.0-SNAPSHOT.jar; lib/org.apache.felix.ipojo.ant-1.7.0-SNAPSHOT.jar;" />
- /></p>
-<div class="codehilite"><pre><span class="n">h2</span><span class="o">.</span> <span class="n">Callbacks</span> <span class="n">order</span><span class="o">.</span>
-
-<span class="n">A</span> <span class="n">lot</span> <span class="n">of</span> <span class="n">handlers</span> <span class="n">define</span> <span class="n">callbacks</span> <span class="n">to</span> <span class="n">notify</span> <span class="n">the</span> <span class="n">implementation</span> <span class="n">class</span><span class="o">.</span> <span class="n">The</span> <span class="s">'core'</span> <span class="n">callbacks</span> <span class="n">are</span> <span class="n">called</span> <span class="n">in</span> <span class="n">the</span> <span class="n">following</span> <span class="n">order:</span>
-<span class="p">{</span><span class="n">code:java</span><span class="p">}</span>
-<span class="nv">@Component</span>
-<span class="nv">@Provides</span>
-<span class="n">public</span> <span class="n">class</span> <span class="n">CallbacksOrder</span> <span class="n">implements</span> <span class="n">MyService</span> <span class="p">{</span>
-
- <span class="n">public</span> <span class="n">CallbacksOrder</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">"1 Constructor"</span><span class="p">);</span>
- <span class="p">}</span>
-
- <span class="nv">@Bind</span>
- <span class="n">public</span> <span class="n">void</span> <span class="nb">bind</span><span class="p">(</span><span class="n">LogService</span> <span class="nb">log</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">"2 Bind "</span> <span class="o">+</span> <span class="nb">log</span><span class="p">);</span>
- <span class="p">}</span>
-
- <span class="nv">@Property</span><span class="p">(</span><span class="n">name</span><span class="o">=</span><span class="s">"prop"</span><span class="p">)</span>
- <span class="n">public</span> <span class="n">void</span> <span class="n">setProp</span><span class="p">(</span><span class="n">String</span> <span class="n">v</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">"3 Set prop "</span> <span class="o">+</span> <span class="n">v</span><span class="p">);</span>
- <span class="p">}</span>
-
- <span class="nv">@Validate</span>
- <span class="n">public</span> <span class="n">void</span> <span class="n">validate</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">"4 Validate"</span><span class="p">);</span>
- <span class="p">}</span>
-
- <span class="nv">@PostRegistration</span>
- <span class="n">public</span> <span class="n">void</span> <span class="n">registered</span><span class="p">(</span><span class="n">ServiceReference</span> <span class="nb">ref</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">"5 Registered"</span><span class="p">);</span>
- <span class="p">}</span>
-
- <span class="sr">//</span> <span class="o">---</span> <span class="n">On</span> <span class="n">Service</span> <span class="n">Departure</span> <span class="o">---</span>
-
- <span class="nv">@Unbind</span>
- <span class="n">public</span> <span class="n">void</span> <span class="n">unbind</span><span class="p">(</span><span class="n">LogService</span> <span class="nb">log</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">"6 Unbind "</span> <span class="o">+</span> <span class="nb">log</span><span class="p">);</span>
- <span class="p">}</span>
-
- <span class="sr">//</span> <span class="n">Remaining</span> <span class="n">of</span> <span class="n">the</span> <span class="n">flow</span>
-
- <span class="nv">@PostUnregistration</span>
- <span class="n">public</span> <span class="n">void</span> <span class="n">unregistered</span><span class="p">(</span><span class="n">ServiceReference</span> <span class="nb">ref</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">"7 Unregistered"</span><span class="p">);</span>
- <span class="p">}</span>
-
- <span class="nv">@Invalidate</span>
- <span class="n">public</span> <span class="n">void</span> <span class="n">invalidate</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">"8 Invalidate"</span><span class="p">);</span>
- <span class="p">}</span>
-
- <span class="sr">//</span> <span class="o">---</span> <span class="n">End</span> <span class="n">of</span> <span class="n">the</span> <span class="n">callback</span> <span class="n">order</span>
-
- <span class="n">public</span> <span class="n">void</span> <span class="n">doNothing</span><span class="p">()</span> <span class="p">{</span>
- <span class="sr">//</span> <span class="n">Do</span> <span class="n">nothing</span><span class="o">...</span>
- <span class="p">}</span>
+<h2 id="callbacks-order">Callbacks order.</h2>
+<p>A lot of handlers define callbacks to notify the implementation class. The 'core' callbacks are called in the following order:</p>
+<div class="codehilite"><pre><span class="nd">@Component</span>
+<span class="nd">@Provides</span>
+<span class="kd">public</span> <span class="kd">class</span> <span class="nc">CallbacksOrder</span> <span class="kd">implements</span> <span class="n">MyService</span> <span class="o">{</span>
+
+ <span class="kd">public</span> <span class="nf">CallbacksOrder</span><span class="o">()</span> <span class="o">{</span>
+ <span class="n">System</span><span class="o">.</span><span class="na">out</span><span class="o">.</span><span class="na">println</span><span class="o">(</span><span class="s">"1 Constructor"</span><span class="o">);</span>
+ <span class="o">}</span>
+
+ <span class="nd">@Bind</span>
+ <span class="kd">public</span> <span class="kt">void</span> <span class="nf">bind</span><span class="o">(</span><span class="n">LogService</span> <span class="n">log</span><span class="o">)</span> <span class="o">{</span>
+ <span class="n">System</span><span class="o">.</span><span class="na">out</span><span class="o">.</span><span class="na">println</span><span class="o">(</span><span class="s">"2 Bind "</span> <span class="o">+</span> <span class="n">log</span><span class="o">);</span>
+ <span class="o">}</span>
+
+ <span class="nd">@Property</span><span class="o">(</span><span class="n">name</span><span class="o">=</span><span class="s">"prop"</span><span class="o">)</span>
+ <span class="kd">public</span> <span class="kt">void</span> <span class="nf">setProp</span><span class="o">(</span><span class="n">String</span> <span class="n">v</span><span class="o">)</span> <span class="o">{</span>
+ <span class="n">System</span><span class="o">.</span><span class="na">out</span><span class="o">.</span><span class="na">println</span><span class="o">(</span><span class="s">"3 Set prop "</span> <span class="o">+</span> <span class="n">v</span><span class="o">);</span>
+ <span class="o">}</span>
+
+ <span class="nd">@Validate</span>
+ <span class="kd">public</span> <span class="kt">void</span> <span class="nf">validate</span><span class="o">()</span> <span class="o">{</span>
+ <span class="n">System</span><span class="o">.</span><span class="na">out</span><span class="o">.</span><span class="na">println</span><span class="o">(</span><span class="s">"4 Validate"</span><span class="o">);</span>
+ <span class="o">}</span>
+
+ <span class="nd">@PostRegistration</span>
+ <span class="kd">public</span> <span class="kt">void</span> <span class="nf">registered</span><span class="o">(</span><span class="n">ServiceReference</span> <span class="n">ref</span><span class="o">)</span> <span class="o">{</span>
+ <span class="n">System</span><span class="o">.</span><span class="na">out</span><span class="o">.</span><span class="na">println</span><span class="o">(</span><span class="s">"5 Registered"</span><span class="o">);</span>
+ <span class="o">}</span>
+
+ <span class="c1">// --- On Service Departure ---</span>
+
+ <span class="nd">@Unbind</span>
+ <span class="kd">public</span> <span class="kt">void</span> <span class="nf">unbind</span><span class="o">(</span><span class="n">LogService</span> <span class="n">log</span><span class="o">)</span> <span class="o">{</span>
+ <span class="n">System</span><span class="o">.</span><span class="na">out</span><span class="o">.</span><span class="na">println</span><span class="o">(</span><span class="s">"6 Unbind "</span> <span class="o">+</span> <span class="n">log</span><span class="o">);</span>
+ <span class="o">}</span>
+
+ <span class="c1">// Remaining of the flow</span>
+
+ <span class="nd">@PostUnregistration</span>
+ <span class="kd">public</span> <span class="kt">void</span> <span class="nf">unregistered</span><span class="o">(</span><span class="n">ServiceReference</span> <span class="n">ref</span><span class="o">)</span> <span class="o">{</span>
+ <span class="n">System</span><span class="o">.</span><span class="na">out</span><span class="o">.</span><span class="na">println</span><span class="o">(</span><span class="s">"7 Unregistered"</span><span class="o">);</span>
+ <span class="o">}</span>
+
+ <span class="nd">@Invalidate</span>
+ <span class="kd">public</span> <span class="kt">void</span> <span class="nf">invalidate</span><span class="o">()</span> <span class="o">{</span>
+ <span class="n">System</span><span class="o">.</span><span class="na">out</span><span class="o">.</span><span class="na">println</span><span class="o">(</span><span class="s">"8 Invalidate"</span><span class="o">);</span>
+ <span class="o">}</span>
+
+ <span class="c1">// --- End of the callback order</span>
+
+ <span class="kd">public</span> <span class="kt">void</span> <span class="nf">doNothing</span><span class="o">()</span> <span class="o">{</span>
+ <span class="c1">// Do nothing...</span>
+ <span class="o">}</span>
-<span class="p">}</span>
+<span class="o">}</span>
</pre></div>
-<h2 id="disabling-proxies-in-ipojo-1643">Disabling proxies in iPOJO 1.6+</h2>
+<h2 id="disabling-proxies-in-ipojo-16">Disabling proxies in iPOJO 1.6+</h2>
<p>iPOJO 1.6.0 has generalized the proxy usage. However this mechanism can be disabled.</p>
-<p>To disable the proxies on the entire framework, just set the property <code>ipojo.proxy</code> to <code>disabled</code> (this set the default 'proxy' value). This property is either a system property (<code>\-Dipojo.proxy=disabled</code> in the command line) or a framework property (given to the framework during its initialization).</p>
-<p>You can also disable proxies for specific dependencies by using the <code>proxy</code> attribute:
-{code:java}
-@Requires(proxy=false)
-private LogService log</p>
-<div class="codehilite"><pre><span class="ow">or</span>
-<span class="p">{</span><span class="n">code:xml</span><span class="p">}</span>
-<span class="o"><</span><span class="n">requires</span> <span class="n">field</span><span class="o">=</span><span class="s">"log"</span> <span class="n">proxy</span><span class="o">=</span><span class="s">"false"</span><span class="o">/></span>
+<p>To disable the proxies on the entire framework, just set the property <code>ipojo.proxy</code> to <code>disabled</code> (this set the default 'proxy' value). This property is either a system property (<code>-Dipojo.proxy=disabled</code> in the command line) or a framework property (given to the framework during its initialization).</p>
+<p>You can also disable proxies for specific dependencies by using the <code>proxy</code> attribute:</p>
+<div class="codehilite"><pre><span class="nd">@Requires</span><span class="o">(</span><span class="n">proxy</span><span class="o">=</span><span class="kc">false</span><span class="o">)</span>
+<span class="kd">private</span> <span class="n">LogService</span> <span class="n">log</span>
+</pre></div>
+
+
+<p>or</p>
+<div class="codehilite"><pre><span class="nt"><requires</span> <span class="na">field=</span><span class="s">"log"</span> <span class="na">proxy=</span><span class="s">"false"</span><span class="nt">/></span>
</pre></div>
@@ -291,22 +306,22 @@ private LogService log</p>
<h2 id="use-dynamic-proxies-instead-of-smart-proxies">Use dynamic proxies instead of smart proxies</h2>
<p>Smart proxies are generated on the fly using bytecode generation. However this mechanism may not be always supported by the VM (like Dalvik (Android)). To disabled smart proxies (used by default) and use dynamic proxy instead, set the property <code>ipojo.proxy.type</code> to <code>dynamic-proxy</code>. This property is either a system property or a framework property.</p>
<h2 id="can-i-use-ipojo-with-other-osgi-implementations">Can I use iPOJO with other OSGi implementations?</h2>
-<p>iPOJO relies on the OSGi R4.1 specification, so works on any compliant implementation. Moreover, iPOJO is weekly tested on Apache Felix, Eclipse Equinox and Knopflerfish..
-For further information, refer to the <a href="/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-supportedosgi.html">supported OSGi implementations</a> page and on this [blog|http://ipojo-dark-side.blogspot.com/2008/11/lessons-learned-from-ipojo-testing.html] post.</p>
+<p>iPOJO relies on the OSGi R4.1 specification, so works on any compliant implementation. Moreover, iPOJO is weekly tested on Apache Felix, Eclipse Equinox and Knopflerfish..</p>
+<p>For further information, refer to the <a href="/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-supportedosgi.html">supported OSGi implementations</a> page and on this [blog|http://ipojo-dark-side.blogspot.com/2008/11/lessons-learned-from-ipojo-testing.html] post.</p>
<h2 id="detecting-optional-service-unavailability">Detecting optional service unavailability</h2>
<p>Sometimes it is useful to check if an optional service dependency is fulfilled or not. In order to propose a pretty simple development model, iPOJO injects proxies by default which avoid such check (Because proxies hide such details). By disabling proxies, you can easily check to unavailability.</p>
<ul>
<li>
-<p>First, disable the proxy injection:
-{code:java}
+<p>First, disable the proxy injection:</p>
+<p>:::java
@Requires(proxy=false)
private LogService log;</p>
-<ul>
-<li>The injected object will be a direct reference. By default, iPOJO injects a object, on which you can call service method without checking for . To detect Nullable objects, just use
-{code:java}
+</li>
+<li>
+<p>The injected object will be a direct reference. By default, iPOJO injects a <code>Nullable</code> object, on which you can call service method without checking for <code>null</code>. To detect Nullable objects, just use <code>instanceof</code></p>
+<p>:::java
@Requires(proxy=false)
-private LogService log;</li>
-</ul>
+private LogService log;</p>
<p>public void doSomething() {
if (log instanceof Nullable) {
// Service unavailable
@@ -316,12 +331,10 @@ private LogService log;</li>
}</p>
</li>
<li>
-<p>If you prefer injecting <code>null</code> instead of a <code>Nullable</code>, just disable Nullable injection too. However, be care to check for <code>null</code> before each invocation.
-{code:java}
+<p>If you prefer injecting <code>null</code> instead of a <code>Nullable</code>, just disable Nullable injection too. However, be care to check for <code>null</code> before each invocation.</p>
+<p>:::java
@Requires(proxy=false, nullable=false)
private LogService log;</p>
-</li>
-</ul>
<p>public void doSomething() {
if (log == null) {
// Service unavailable
@@ -329,19 +342,20 @@ private LogService log;</p>
// Service available
}
}</p>
-<div class="codehilite"><pre><span class="n">h2</span><span class="o">.</span> <span class="n">Setting</span> <span class="n">the</span> <span class="n">iPOJO</span> <span class="nb">log</span> <span class="n">level</span>
-
-<span class="n">By</span> <span class="n">default</span><span class="p">,</span> <span class="n">iPOJO</span> <span class="n">logs</span> <span class="n">only</span> <span class="n">warning</span> <span class="ow">and</span> <span class="n">error</span> <span class="n">messages</span><span class="o">.</span> <span class="n">There</span> <span class="n">are</span> <span class="n">two</span> <span class="n">different</span> <span class="n">methods</span> <span class="n">to</span> <span class="n">configure</span> <span class="n">the</span> <span class="nb">log</span> <span class="n">level</span><span class="o">.</span> <span class="n">First</span><span class="p">,</span> <span class="n">you</span> <span class="n">can</span> <span class="n">set</span> <span class="n">the</span> <span class="n">global</span> <span class="nb">log</span> <span class="n">level</span> <span class="n">by</span> <span class="n">setting</span> <span class="n">the</span> <span class="n">_ipojo</span><spa
n class="o">.</span><span class="nb">log</span><span class="o">.</span><span class="n">level_</span> <span class="nb">system</span> <span class="n">property</span><span class="o">.</span> <span class="n">This</span> <span class="n">replaces</span> <span class="n">the</span> <span class="n">default</span> <span class="nb">log</span> <span class="n">level</span> <span class="p">(</span><span class="n">warning</span><span class="p">)</span><span class="o">.</span> <span class="n">All</span> <span class="n">iPOJO</span> <span class="n">instances</span> <span class="n">will</span> <span class="n">be</span> <span class="n">impacted</span><span class="o">.</span> <span class="n">However</span><span class="p">,</span> <span class="nb">each</span> <span class="n">bundle</span> <span class="n">containing</span> <span class="n">component</span> <span class="n">types</span> <span class="n">can</span> <span class="n">specify</span> <span class="n">a</span> <span class="n">different</spa
n> <span class="nb">log</span> <span class="n">level</span><span class="o">.</span> <span class="n">To</span> <span class="n">set</span> <span class="n">this</span> <span class="n">level</span><span class="p">,</span> <span class="n">add</span> <span class="n">the</span> <span class="n">_ipojo</span><span class="o">-</span><span class="nb">log</span><span class="o">-</span><span class="n">level_</span> <span class="n">header</span> <span class="n">in</span> <span class="n">your</span> <span class="n">manifest</span><span class="o">.</span> <span class="n">The</span> <span class="n">possible</span> <span class="nb">values</span> <span class="k">for</span> <span class="n">these</span> <span class="n">two</span> <span class="n">properties</span> <span class="n">are:</span>
-<span class="o">*</span> <span class="n">info</span>
+</li>
+</ul>
+<h2 id="setting-the-ipojo-log-level">Setting the iPOJO log level</h2>
+<p>By default, iPOJO logs only warning and error messages. There are two different methods to configure the log level. First, you can set the global log level by setting the <em>ipojo.log.level</em> system property. This replaces the default log level (warning). All iPOJO instances will be impacted. However, each bundle containing component types can specify a different log level. To set this level, add the <em>ipojo-log-level</em> header in your manifest. The possible values for these two properties are:</p>
+<div class="codehilite"><pre><span class="o">*</span> <span class="n">info</span>
<span class="o">*</span> <span class="n">debug</span>
<span class="o">*</span> <span class="n">warning</span> <span class="p">(</span><span class="n">default</span><span class="p">)</span>
<span class="o">*</span> <span class="n">error</span>
+</pre></div>
-<span class="n">h2</span><span class="o">.</span> <span class="n">Installing</span> <span class="n">iPOJO</span> <span class="n">in</span> <span class="n">Service</span> <span class="n">Mix</span> <span class="n">Kernel</span>
-<span class="n">You</span> <span class="n">can</span> <span class="k">use</span> <span class="n">iPOJO</span> <span class="n">in</span> <span class="n">Service</span> <span class="n">Mix</span> <span class="n">Kernel</span><span class="o">.</span> <span class="n">To</span> <span class="n">deploy</span> <span class="ow">and</span> <span class="n">start</span> <span class="n">it</span><span class="p">,</span> <span class="n">just</span> <span class="n">execute</span> <span class="n">the</span> <span class="n">following</span> <span class="n">command</span> <span class="n">line</span> <span class="n">in</span> <span class="n">the</span> <span class="n">ServiceMix</span> <span class="n">Kernel</span> <span class="n">Shell</span><span class="o">.</span>
-<span class="p">{</span><span class="n">code:xml</span><span class="p">}</span>
-<span class="n">osgi</span> <span class="n">install</span> <span class="o">-</span><span class="n">s</span> <span class="n">mvn:org</span><span class="o">.</span><span class="n">apache</span><span class="o">.</span><span class="n">felix</span><span class="sr">/org.apache.felix.ipojo/</span><span class="mf">1.2.0</span>
+<h2 id="installing-ipojo-in-service-mix-kernel">Installing iPOJO in Service Mix Kernel</h2>
+<p>You can use iPOJO in Service Mix Kernel. To deploy and start it, just execute the following command line in the ServiceMix Kernel Shell.</p>
+<div class="codehilite"><pre>osgi install -s mvn:org.apache.felix/org.apache.felix.ipojo/1.2.0
</pre></div>
@@ -350,37 +364,43 @@ private LogService log;</p>
<p>Thanks to File install you can create, disposed and reconfigure instances from <em>cfg</em> files. You can also reconfiguring a creatged instance (configured to expose a <a href="http://felix.apache.org/site/configuration-handler.html#ConfigurationHandler-ExposingaManagedService">ManagedService</a>) with <em>cfg</em> files too. More information about this topic is available [here|http://ipojo-dark-side.blogspot.com/2009/04/ipojo-and-file-install-configuring.html].</p>
<h2 id="ipojo-handler-start-level">iPOJO handler <em>start</em> level</h2>
<p>iPOJO Handlers have a <em>start</em> level. This is <em>not</em> the <code>OSGi Start Level</code>. This level is used to determine in which order handler are configured, started and stopped. Handlers with a low level are configured and started before handlers with a high level. Moreover they are stopped after handlers with a high level. By default, handlers have no level. It means that they have the maximum level (<code>Integer.MAX</code>).</p>
-<p>Here are the levels of core handlers:
-<em> Service Dependency: 0 (minimum level)
-</em> Lifecycle Callback: 1
-<em> Configuration Properties: 1
-</em> Service Providing: 3
-<em> Controller Handler: no level (Integer.MAX)
-</em> Architecture Handler: no level (Integer.MAX)</p>
-<p>From these levels, we can see that bind methods will be called before set methods from configuration properties. So, when a POJO objects, callback are called in this order:
-1. bind methods
-1. validate method
-1. setter methods from instance configuration</p>
-<div class="info" markdown="1">
-**Changes in the 1.3.0-SNAPSHOT**
+<p>Here are the levels of core handlers:</p>
+<ul>
+<li>Service Dependency: 0 (minimum level)</li>
+<li>Lifecycle Callback: 1</li>
+<li>Configuration Properties: 1</li>
+<li>Service Providing: 3</li>
+<li>Controller Handler: no level (Integer.MAX)</li>
+<li>Architecture Handler: no level (Integer.MAX)</li>
+</ul>
+<p>From these levels, we can see that bind methods will be called before set methods from configuration properties. So, when a POJO objects, callback are called in this order:</p>
+<ol>
+<li>bind methods</li>
+<li>validate method</li>
+<li>setter methods from instance configuration</li>
+</ol>
+<div class="alert alert-info info" markdown="1">
+<h4>Changes in the 1.3.0-SNAPSHOT</h4>
iPOJO 1.3.0-SNAPSHOT sets the lifecycle callback handler level to 2. So, setter methods from instance properties are called before the validate method.
</div>
<h2 id="why-does-my-bundle-import-unused-packages">Why does my bundle import unused packages?</h2>
-<p>If you check iPOJO bundle imported packages, you will see that some packages where added:
-<em> org.apache.felix.ipojo;version= 1.2.0
-</em> org.apache.felix.ipojo.architecture;version= 1.2.0
-<em> org.osgi.service.cm;version=1.2
-</em> org.osgi.service.log;version=1.3</p>
-<p>The <code>org.apache.felix.ipojo</code> package is the main iPOJO package. Manipulated class use it to get access to injected values. The <code>org.apache.felix.ipojo.architecture</code> package is used to expose <em>Architecture</em> service (allowing instance introspection). This service is exposed with the bundle context from the bundle declaring the component type.
-The <code>org.osgi.service.cm</code> package is imported to publish <em>ManagedService</em> and <em>ManagedServiceFactory</em> with the bundle context from the bundle declaring the component type. So, if you look for services exposed by a bundle declaring component types, you will see <em>ManagedServiceFactory</em> services.
+<p>If you check iPOJO bundle imported packages, you will see that some packages where added:</p>
+<ul>
+<li>org.apache.felix.ipojo;version= 1.2.0</li>
+<li>org.apache.felix.ipojo.architecture;version= 1.2.0</li>
+<li>org.osgi.service.cm;version=1.2</li>
+<li>org.osgi.service.log;version=1.3</li>
+</ul>
+<p>The <code>org.apache.felix.ipojo</code> package is the main iPOJO package. Manipulated class use it to get access to injected values. The <code>org.apache.felix.ipojo.architecture</code> package is used to expose <em>Architecture</em> service (allowing instance introspection). This service is exposed with the bundle context from the bundle declaring the component type.</p>
+<p>The <code>org.osgi.service.cm</code> package is imported to publish <em>ManagedService</em> and <em>ManagedServiceFactory</em> with the bundle context from the bundle declaring the component type. So, if you look for services exposed by a bundle declaring component types, you will see <em>ManagedServiceFactory</em> services.
Finally, the <code>org.osgi.service.log</code> is imported because iPOJO delegates log to a log service (if available). This service is get from the bundle context from the bundle declaring the component type. So, to get this service, the package of the service interface is imported. Then, according to implementations, log services may get the bundle logging the message.</p>
<h2 id="how-does-ipojo-compare-to-declarative-services-or-blueprint">How does iPOJO compare to Declarative Services or Blueprint?</h2>
<p>The following table highlights some of the features of each system, it does not attempt to highlight every feature of each.</p>
<table>
<thead>
<tr>
-<th>Dependency injection</th>
+<th>Dependency injection </th>
<th>Declarative Services</th>
<th>Blueprint</th>
<th>iPOJO</th>
@@ -429,18 +449,18 @@ Finally, the <code>org.osgi.service.log<
<td>No</td>
<td>Yes</td>
</tr>
+</tbody>
+</table>
+<table>
+<thead>
<tr>
-<td>Lifecycle</td>
-<td>Declarative Services</td>
-<td>Blueprint</td>
-<td>iPOJO</td>
-</tr>
-<tr>
-<td>--</td>
-<td>--</td>
-<td>--</td>
-<td>--</td>
+<th>Lifecycle</th>
+<th>Declarative Services</th>
+<th>Blueprint</th>
+<th>iPOJO</th>
</tr>
+</thead>
+<tbody>
<tr>
<td>Callbacks (activate/deactivate)</td>
<td>Yes</td>
@@ -483,18 +503,18 @@ Finally, the <code>org.osgi.service.log<
<td>No</td>
<td>Yes</td>
</tr>
+</tbody>
+</table>
+<table>
+<thead>
<tr>
-<td>Configuration</td>
-<td>Declarative Services</td>
-<td>Blueprint</td>
-<td>iPOJO</td>
-</tr>
-<tr>
-<td>--</td>
-<td>--</td>
-<td>--</td>
-<td>--</td>
+<th>Configuration</th>
+<th>Declarative Services</th>
+<th>Blueprint</th>
+<th>iPOJO</th>
</tr>
+</thead>
+<tbody>
<tr>
<td>Property configuration</td>
<td>No</td>
@@ -513,18 +533,18 @@ Finally, the <code>org.osgi.service.log<
<td>No</td>
<td>Yes</td>
</tr>
+</tbody>
+</table>
+<table>
+<thead>
<tr>
-<td>Services</td>
-<td>Declarative Services</td>
-<td>Blueprint</td>
-<td>iPOJO</td>
-</tr>
-<tr>
-<td>--</td>
-<td>--</td>
-<td>--</td>
-<td>--</td>
+<th>Services</th>
+<th>Declarative Services</th>
+<th>Blueprint</th>
+<th>iPOJO</th>
</tr>
+</thead>
+<tbody>
<tr>
<td>Custom attribute type</td>
<td>No</td>
@@ -543,18 +563,18 @@ Finally, the <code>org.osgi.service.log<
<td>No</td>
<td>Yes</td>
</tr>
+</tbody>
+</table>
+<table>
+<thead>
<tr>
-<td>Component description</td>
-<td>Declarative Services</td>
-<td>Blueprint</td>
-<td>iPOJO</td>
-</tr>
-<tr>
-<td>--</td>
-<td>--</td>
-<td>--</td>
-<td>--</td>
+<th>Component description</th>
+<th>Declarative Services</th>
+<th>Blueprint</th>
+<th>iPOJO</th>
</tr>
+</thead>
+<tbody>
<tr>
<td>XML</td>
<td>Yes</td>
@@ -573,18 +593,18 @@ Finally, the <code>org.osgi.service.log<
<td>No</td>
<td>Yes</td>
</tr>
+</tbody>
+</table>
+<table>
+<thead>
<tr>
-<td>Nonfunctional</td>
-<td>Declarative Services</td>
-<td>Blueprint</td>
-<td>iPOJO</td>
-</tr>
-<tr>
-<td>--</td>
-<td>--</td>
-<td>--</td>
-<td>--</td>
+<th>Nonfunctional</th>
+<th>Declarative Services</th>
+<th>Blueprint</th>
+<th>iPOJO</th>
</tr>
+</thead>
+<tbody>
<tr>
<td>Multiple providers</td>
<td>Yes</td>
@@ -607,7 +627,7 @@ Finally, the <code>org.osgi.service.log<
may be trademarks or registered trademarks of their respective owners.
</div>
<div class="timestamp span3 offset2">
- Rev. 1441864 by fmeschbe on Sun, 3 Feb 2013 06:44:40 +0000
+ Rev. 1445514 by clement on Wed, 13 Feb 2013 09:20:49 +0000
</div>
</div>
</footer>
Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/using-xml-schemas.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/using-xml-schemas.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/using-xml-schemas.html Wed Feb 13 09:20:58 2013
@@ -117,7 +117,7 @@
<ul class="dropdown-menu" id="swatch-menu">
<li><a href="/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/ipojo-ant-task.html">Ant Task</a></li>
<li><a href="">Eclipse Plugin</a></li>
- <li><a href="">Maven Plugin</a></li>
+ <li><a href="/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/ipojo-maven-plug-in.html">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>
@@ -155,19 +155,50 @@
<div class="content">
<h1 id="using-xml-schemas">Using XML Schemas</h1>
<p><em>iPOJO provides XML schemas to check iPOJO descriptors (i.e. metadata.xml). Several schemas are provided in order to describe the core syntax, compositions and external handlers.</em></p>
-<p>{center}
-| Schema | URL |
-|--|--|
-| iPOJO Core | <a href="http://felix.apache.org/ipojo/schemas/CURRENT/core.xsd">http://felix.apache.org/ipojo/schemas/CURRENT/core.xsd</a> |
-| iPOJO Composite | <a href="http://felix.apache.org/ipojo/schemas/CURRENT/composite.xsd">http://felix.apache.org/ipojo/schemas/CURRENT/composite.xsd</a> |
-| Temporal Dependency Handler | <a href="http://felix.apache.org/ipojo/schemas/CURRENT/temporal.xsd">http://felix.apache.org/ipojo/schemas/CURRENT/temporal.xsd</a> |
-| Whiteboard pattern handler | <a href="http://felix.apache.org/ipojo/schemas/CURRENT/whiteboard-pattern.xsd">http://felix.apache.org/ipojo/schemas/CURRENT/whiteboard-pattern.xsd</a> |
-| Extender pattern handler | <a href="http://felix.apache.org/ipojo/schemas/CURRENT/extender-pattern.xsd">http://felix.apache.org/ipojo/schemas/CURRENT/extender-pattern.xsd</a> |
-| Event Admin handlers | <a href="http://felix.apache.org/ipojo/schemas/CURRENT/event-admin.xsd">http://felix.apache.org/ipojo/schemas/CURRENT/event-admin.xsd</a> |
-| JMX handler | <a href="http://felix.apache.org/ipojo/schemas/CURRENT/jmx.xsd">http://felix.apache.org/ipojo/schemas/CURRENT/jmx.xsd</a> |
-{center}</p>
-<p><em>Note:</em> the schemas are also provided inside implicated bundles.
-<em>Note:</em> to use the 'dev' schemas, replace <code>CURRENT</code> by <code>SNAPSHOT</code> in the URL.
+<table>
+<thead>
+<tr>
+<th>Schema</th>
+<th>URL</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>iPOJO Core</td>
+<td><a href="http://felix.apache.org/ipojo/schemas/CURRENT/core.xsd">http://felix.apache.org/ipojo/schemas/CURRENT/core.xsd</a></td>
+</tr>
+<tr>
+<td>iPOJO Composite</td>
+<td><a href="http://felix.apache.org/ipojo/schemas/CURRENT/composite.xsd">http://felix.apache.org/ipojo/schemas/CURRENT/composite.xsd</a></td>
+</tr>
+<tr>
+<td>Temporal Dependency Handler</td>
+<td><a href="http://felix.apache.org/ipojo/schemas/CURRENT/temporal.xsd">http://felix.apache.org/ipojo/schemas/CURRENT/temporal.xsd</a></td>
+</tr>
+<tr>
+<td>Whiteboard pattern handler</td>
+<td><a href="http://felix.apache.org/ipojo/schemas/CURRENT/whiteboard-pattern.xsd">http://felix.apache.org/ipojo/schemas/CURRENT/whiteboard-pattern.xsd</a></td>
+</tr>
+<tr>
+<td>Extender pattern handler</td>
+<td><a href="http://felix.apache.org/ipojo/schemas/CURRENT/extender-pattern.xsd">http://felix.apache.org/ipojo/schemas/CURRENT/extender-pattern.xsd</a></td>
+</tr>
+<tr>
+<td>Event Admin handlers</td>
+<td><a href="http://felix.apache.org/ipojo/schemas/CURRENT/event-admin.xsd">http://felix.apache.org/ipojo/schemas/CURRENT/event-admin.xsd</a></td>
+</tr>
+<tr>
+<td>JMX handler</td>
+<td><a href="http://felix.apache.org/ipojo/schemas/CURRENT/jmx.xsd">http://felix.apache.org/ipojo/schemas/CURRENT/jmx.xsd</a></td>
+</tr>
+<tr>
+<td> </td>
+<td></td>
+</tr>
+</tbody>
+</table>
+<p><em>Note:</em> the schemas are also provided inside implicated bundles.</p>
+<p><em>Note:</em> to use the 'dev' schemas, replace <code>CURRENT</code> by <code>SNAPSHOT</code> in the URL.
To use those schemas you have to declares those schemas in your metadata.xml file such as in the next snippet using the iPOJO core XML-schema:</p>
<div class="codehilite"><pre><span class="nt"><ipojo</span>
<span class="na">xmlns:xsi=</span><span class="s">"http://www.w3.org/2001/XMLSchema-instance"</span>
@@ -179,7 +210,7 @@ To use those schemas you have to declare
</pre></div>
-<p>First, declares the 'XMLSChema-instance' namespace. Then, declares used namespaces and schemas in the 'xsi:schemaLocation' attribute. This attribute contains pairs 'namespace url' separated by spaces. Finally, declares the default namespace to "org.apache.felix.ipojo".
+<p>First, declare the 'XMLSChema-instance' namespace. Then, declares used namespaces and schemas in the 'xsi:schemaLocation' attribute. This attribute contains pairs 'namespace url' separated by spaces. Finally, declares the default namespace to "org.apache.felix.ipojo".
You can also use several schemas in the same descriptor by using a header like:</p>
<div class="codehilite"><pre><span class="nt"><ipojo</span> <span class="na">xmlns:xsi=</span><span class="s">"http://www.w3.org/2001/XMLSchema-instance"</span>
<span class="na">xsi:schemaLocation=</span><span class="s">"org.apache.felix.ipojo http://felix.apache.org/ipojo/schemas/CURRENT/core.xsd</span>
@@ -200,10 +231,10 @@ You can also use several schemas in the
</pre></div>
-<p>The only difference is contained in the 'schemaLocation' attribute, which contains several pairs. You also need to declare the namespace of the used external handler.
-If you declare schemas, the iPOJO manipulator automatically checks the validity of the descriptor against the declared schemas. Moreover, if you use 'advanced' XML Editor supporting schemas, editing iPOJO descriptors should be eased with auto-completion features.</p>
+<p>The only difference is contained in the 'schemaLocation' attribute, which contains several pairs. You also need to declare the namespace of the used external handler.</p>
+<p>If you declare schemas, the iPOJO manipulator automatically checks the validity of the descriptor against the declared schemas. Moreover, if you use 'advanced' XML Editor supporting schemas, editing iPOJO descriptors should be eased with auto-completion features.</p>
<h2 id="avoid-downloading-xml-schemas-during-the-build-process">Avoid downloading XML Schemas during the build process</h2>
-<p>The manipulator embeds the iPOJO XML Schemas to avoid using a network connection to download them during the validation process. Keep the same url, the manipulator will just resolve the URL differently to use embedded schemas. You can also skipped this shortcut thanks the the <code>ignoreEmbeddedSchemas</code> parameter (refer to the <a href="/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/ipojo-ant-task.html">ant task guide</a> and to the [maven plugin guide|iPOJO Maven Plug-in] for further information about configuration).</p>
+<p>The manipulator embeds the iPOJO XML Schemas to avoid using a network connection to download them during the validation process. Keep the same url, the manipulator will just resolve the URL differently to use embedded schemas. You can also skipped this shortcut thanks the the <code>ignoreEmbeddedSchemas</code> parameter (refer to the <a href="/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/ipojo-ant-task.html">ant task guide</a> and to the <a href="/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/ipojo-maven-plug-in.html">maven plugin guide</a> for further information about configuration).</p>
</div>
</div>
@@ -218,7 +249,7 @@ If you declare schemas, the iPOJO manipu
may be trademarks or registered trademarks of their respective owners.
</div>
<div class="timestamp span3 offset2">
- Rev. 1441864 by fmeschbe on Sun, 3 Feb 2013 06:44:40 +0000
+ Rev. 1445514 by clement on Wed, 13 Feb 2013 09:20:49 +0000
</div>
</div>
</footer>
Modified: websites/staging/felix/trunk/content/ipojo/site/button.html
==============================================================================
--- websites/staging/felix/trunk/content/ipojo/site/button.html (original)
+++ websites/staging/felix/trunk/content/ipojo/site/button.html Wed Feb 13 09:20:58 2013
@@ -1,2 +1,2 @@
<html><head>
-<meta http-equiv="content-type" content="text/html; charset=UTF-8"></head><body></body></html>
\ No newline at end of file
+<meta http-equiv="content-type" content="text/html; charset=UTF-8"></head><body></body></html>