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/04/25 14:13:26 UTC
svn commit: r859846 - in /websites/staging/felix/trunk/content: ./
documentation/subprojects/apache-felix-ipojo/
documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-devguide/
documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-t...
Author: buildbot
Date: Thu Apr 25 12:13:25 2013
New Revision: 859846
Log:
Staging update by buildbot for felix
Added:
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/ipojo-webconsole-quicktart-distribution.zip (with props)
Modified:
websites/staging/felix/trunk/content/ (props changed)
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-devguide/how-to-use-ipojo-manipulation-metadata.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/ipojo-webconsole-plugin.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/architecture-handler.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/controller-lifecycle-handler.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/providing-osgi-services.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/developing-camel-mediators-with-ipojo.html
Propchange: websites/staging/felix/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Apr 25 12:13:25 2013
@@ -1 +1 @@
-1475684
+1475720
Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-devguide/how-to-use-ipojo-manipulation-metadata.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-devguide/how-to-use-ipojo-manipulation-metadata.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-devguide/how-to-use-ipojo-manipulation-metadata.html Thu Apr 25 12:13:25 2013
@@ -225,7 +225,7 @@
<li>For primitive types : int, long, short, byte, char, double, float, boolean</li>
<li>For primitives type arrays : int[], long[], short[], byte[], char[], double[], float[], boolean[]</li>
<li>For object : qualified class name as java.lang.String</li>
-<li>For object arrays : the qualified class name of the content type followed by <a href=""></a> as java.lang.String[]</li>
+<li>For object arrays : the qualified class name of the content type followed by [] as java.lang.String[]</li>
</ul>
<p>Array types are different from Java internal/reflective array types. To get the internal/reflective array type for field type you can use the <code>getReflectiveType</code> method.</p>
</div>
@@ -242,7 +242,7 @@
may be trademarks or registered trademarks of their respective owners.
</div>
<div class="timestamp span3 offset2">
- Rev. 1443380 by clement on Thu, 7 Feb 2013 10:01:34 +0000
+ Rev. 1475720 by clement on Thu, 25 Apr 2013 12:13:11 +0000
</div>
</div>
</footer>
Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/ipojo-webconsole-plugin.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/ipojo-webconsole-plugin.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/ipojo-webconsole-plugin.html Thu Apr 25 12:13:25 2013
@@ -186,6 +186,51 @@
<li>iPOJO </li>
<li>The iPOJO Web console plugin</li>
</ul>
+<p>You can download <a href="ipojo-webconsole-quicktart-distribution.zip">this Felix distribution</a> as a deployment example. Unzip the archive and go to the Felix directory to launch Felix:</p>
+<div class="codehilite"><pre><span class="nb">cd </span>ipojo-webconsole-quicktart-1.9.0-SNAPSHOT/felix-framework-4.2.1/
+java -jar bin/felix.jar
+</pre></div>
+
+
+<p>Once launched, you can check the deployed bundles:</p>
+<div class="codehilite"><pre><span class="o">[</span>INFO<span class="o">]</span> Started jetty 6.1.x at port<span class="o">(</span>s<span class="o">)</span> HTTP:8080
+____________________________
+Welcome to Apache Felix Gogo
+
+g! INFO : org.apache.felix.webconsole.plugins.memoryusage <span class="o">(</span>17<span class="o">)</span>: Storing Memory Dumps in /Users/clement/Projects/felix-trunk/ipojo/distributions/ipojo-webconsole-quicktart/target/ipojo-webconsole-quicktart-1.9.0-SNAPSHOT/felix-framework-4.2.1/./felix-cache/bundle17/data/dumps
+INFO : org.apache.felix.webconsole.plugins.memoryusage <span class="o">(</span>17<span class="o">)</span>: Setting Automatic Memory Dump Threshold to 0% <span class="k">for </span>pools <span class="o">[</span>CMS Old Gen, CMS Perm Gen, Code Cache<span class="o">]</span>
+INFO : org.apache.felix.webconsole.plugins.memoryusage <span class="o">(</span>17<span class="o">)</span>: Automatic Memory Dump cannot be <span class="nb">set </span><span class="k">for </span>pools <span class="o">[</span>Par Eden Space, Par Survivor Space<span class="o">]</span>
+INFO : org.apache.felix.webconsole.plugins.memoryusage <span class="o">(</span>17<span class="o">)</span>: Setting Automatic Memory Dump Interval to 21600 seconds
+
+g! lb
+START LEVEL 1
+ ID|State |Level|Name
+ 0|Active | 0|System Bundle <span class="o">(</span>4.2.1<span class="o">)</span>
+ 1|Active | 1|Java Servlet API <span class="o">(</span>2.4.0<span class="o">)</span>
+ 2|Active | 1|Commons FileUpload <span class="o">(</span>1.2.2<span class="o">)</span>
+ 3|Active | 1|Commons IO <span class="o">(</span>2.4.0<span class="o">)</span>
+ 4|Active | 1|Apache Felix Bundle Repository <span class="o">(</span>1.6.6<span class="o">)</span>
+ 5|Active | 1|Apache Felix Gogo Command <span class="o">(</span>0.12.0<span class="o">)</span>
+ 6|Active | 1|Apache Felix Gogo Runtime <span class="o">(</span>0.10.0<span class="o">)</span>
+ 7|Active | 1|Apache Felix Gogo Shell <span class="o">(</span>0.10.0<span class="o">)</span>
+ 8|Active | 1|Apache Felix Http Api <span class="o">(</span>2.2.0<span class="o">)</span>
+ 9|Active | 1|Apache Felix Http Base <span class="o">(</span>2.2.0<span class="o">)</span>
+ 10|Active | 1|Apache Felix Http Jetty <span class="o">(</span>2.2.0<span class="o">)</span>
+ 11|Active | 1|Apache Felix iPOJO <span class="o">(</span>1.8.6<span class="o">)</span>
+ 12|Active | 1|Apache Felix iPOJO Annotations <span class="o">(</span>1.8.6<span class="o">)</span>
+ 13|Active | 1|Apache Felix iPOJO Gogo Command <span class="o">(</span>1.0.1<span class="o">)</span>
+ 14|Active | 1|iPOJO Metadata <span class="o">(</span>1.6.0<span class="o">)</span>
+ 15|Active | 1|Apache Felix iPOJO WebConsole Plugins <span class="o">(</span>1.7.0.SNAPSHOT<span class="o">)</span>
+ 16|Active | 1|Apache Felix Web Management Console <span class="o">(</span>4.0.0<span class="o">)</span>
+ 17|Active | 1|Apache Felix Web Console Memory Usage Plugin <span class="o">(</span>1.0.2<span class="o">)</span>
+ 18|Active | 1|Apache Felix Web Console Package Admin Service Plugin <span class="o">(</span>1.0.0<span class="o">)</span>
+ 19|Active | 1|osgi.cmpn <span class="o">(</span>4.2.0.200908310645<span class="o">)</span>
+ 20|Active | 1|OW2 Chameleon - JSON Bundle <span class="o">(</span>from org.json<span class="o">)</span> <span class="o">(</span>20090911.0.0.0002<span class="o">)</span>
+</pre></div>
+
+
+<p>You access the web console at: http://localhost:8080/system/console/. The login/password are <em>admin</em>/<em>admin</em>. The iPOJO tabs gives you all the iPOJO information of the system. <br />
+</p>
</div>
</div>
@@ -200,7 +245,7 @@
may be trademarks or registered trademarks of their respective owners.
</div>
<div class="timestamp span3 offset2">
- Rev. 1465947 by clement on Tue, 9 Apr 2013 09:37:22 +0000
+ Rev. 1475720 by clement on Thu, 25 Apr 2013 12:13:11 +0000
</div>
</div>
</footer>
Added: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/ipojo-webconsole-quicktart-distribution.zip
==============================================================================
Binary file - no diff available.
Propchange: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/ipojo-webconsole-quicktart-distribution.zip
------------------------------------------------------------------------------
svn:mime-type = application/zip
Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/architecture-handler.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/architecture-handler.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/architecture-handler.html Thu Apr 25 12:13:25 2013
@@ -159,7 +159,7 @@
<div class="container">
<div class="content">
<h1 id="introspection-and-architecture">Introspection and Architecture</h1>
-<p><em>The architecture feature allows obtaining an architectural / component view of your systems. It exposes a snapshot of the present instances & factories, the state of these instances... Moreover; iPOJO defines an 'arch' command displaying this architecture in Felix. You need to install <a href="">the arch command</a>.</em></p>
+<p><em>The architecture feature allows obtaining an architectural / component view of your systems. It exposes a snapshot of the present instances & factories, the state of these instances... Moreover; iPOJO defines an 'arch' command displaying this architecture in Felix. You need to install <a href="/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/ipojo-arch-command.html">the arch command</a>.</em></p>
<div class="toc">
<ul>
<li><a href="#introspection-and-architecture">Introspection and Architecture</a><ul>
@@ -181,12 +181,30 @@
<p>By default, the architecture feature is enabled.</p>
<h2 id="the-arch-command">The "arch" command</h2>
-<p>A Felix command comes with the architecture handler. This command looks for all component exposing the architecture and print the information.</p>
-<div class="codehilite"><pre><span class="nv">arch</span> <span class="o">=</span>> displays instances name & state <span class="o">(</span>equivalent to arch <span class="se">\-</span>instances<span class="o">)</span>
-arch -instance <span class="nv">$instance_name</span> <span class="o">=</span>> displays <span class="nb">complete </span>information about the instance <span class="nv">$instance_name</span>
-arch -factories <span class="o">=</span>> display the list of available factories
-arch -factory <span class="nv">$factory_name</span> <span class="o">=</span>> display <span class="nb">complete </span>information about the factory <span class="nv">$factory_name</span>
-arch -handlers <span class="o">=</span>> list available handlers
+<p>The Gogo commands are the following:</p>
+<ul>
+<li><code>ipojo:instances</code> (or just <code>instances</code>) lists the instances and state</li>
+<li><code>ipojo:instance $instance_name</code> (or just <code>instance $instance_name</code>) displays the complete information about the specified $instance_name</li>
+<li><code>ipojo:factories</code> (or just <code>factories</code>) lists the available public factories</li>
+<li><code>ipojo:factory $factory_name</code> (or just <code>factory $factory_name</code>) displays complete information about the factory $factory_name</li>
+<li><code>ipojo:handlers</code> (or just <code>handlers</code> lists available handlers</li>
+</ul>
+<p>For example:</p>
+<div class="codehilite"><pre><span class="nv">$ </span>instances
+Instance ArchCommand -> valid
+Instance spell.english.EnglishDictionary-0 -> valid
+Instance spell.checker.SpellCheck-0 -> valid
+Instance spell.gui.SpellCheckerGui-0 -> valid
+
+<span class="nv">$ </span>instance spell.checker.SpellCheck-0
+instance component.type<span class="o">=</span><span class="s2">"spell.checker.SpellCheck"</span> <span class="nv">state</span><span class="o">=</span><span class="s2">"valid"</span> <span class="nv">bundle</span><span class="o">=</span><span class="s2">"8"</span> <span class="nv">name</span><span class="o">=</span><span class="s2">"spell.checker.SpellCheck-0"</span>
+ handler <span class="nv">state</span><span class="o">=</span><span class="s2">"valid"</span> <span class="nv">name</span><span class="o">=</span><span class="s2">"org.apache.felix.ipojo.handlers.dependency.DependencyHandler"</span>
+ requires <span class="nv">optional</span><span class="o">=</span><span class="s2">"false"</span> <span class="nv">aggregate</span><span class="o">=</span><span class="s2">"false"</span> <span class="nv">state</span><span class="o">=</span><span class="s2">"resolved"</span> binding-policy<span class="o">=</span><span class="s2">"dynamic"</span> <span class="nv">specification</span><span class="o">=</span><span class="s2">"spell.services.DictionaryService"</span>
+ handler <span class="nv">state</span><span class="o">=</span><span class="s2">"valid"</span> <span class="nv">name</span><span class="o">=</span><span class="s2">"org.apache.felix.ipojo.handlers.providedservice.ProvidedServiceHandler"</span>
+ provides service.id<span class="o">=</span><span class="s2">"36"</span> <span class="nv">state</span><span class="o">=</span><span class="s2">"registered"</span> <span class="nv">specifications</span><span class="o">=</span><span class="s2">"[spell.services.SpellChecker]"</span>
+ property <span class="nv">value</span><span class="o">=</span><span class="s2">"spell.checker.SpellCheck"</span> <span class="nv">name</span><span class="o">=</span><span class="s2">"factory.name"</span>
+ property <span class="nv">value</span><span class="o">=</span><span class="s2">"spell.checker.SpellCheck-0"</span> <span class="nv">name</span><span class="o">=</span><span class="s2">"instance.name"</span>
+ handler <span class="nv">state</span><span class="o">=</span><span class="s2">"valid"</span> <span class="nv">name</span><span class="o">=</span><span class="s2">"org.apache.felix.ipojo.handlers.architecture.ArchitectureHandler"</span>
</pre></div>
@@ -207,7 +225,7 @@ arch -handlers <span class="o">=</span>&
may be trademarks or registered trademarks of their respective owners.
</div>
<div class="timestamp span3 offset2">
- Rev. 1443565 by clement on Thu, 7 Feb 2013 15:43:47 +0000
+ Rev. 1475720 by clement on Thu, 25 Apr 2013 12:13:11 +0000
</div>
</div>
</footer>
Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/controller-lifecycle-handler.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/controller-lifecycle-handler.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/controller-lifecycle-handler.html Thu Apr 25 12:13:25 2013
@@ -159,7 +159,7 @@
<div class="container">
<div class="content">
<h1 id="lifecycle-controller-handler">Lifecycle Controller Handler</h1>
-<p><em>The lifecycle controller allows a component implementation to participate to the instance lifecycle. So, you can immediately decide to stop an instance if the configuration is incorrect (correct properties, accessible resources...). The licecyel controller impacts the instance lifecycle, if you want to impact only the registered service, have a look to the service controller (<a href="">service providing</a>).</em></p>
+<p><em>The lifecycle controller allows a component implementation to participate to the instance lifecycle. So, you can immediately decide to stop an instance if the configuration is incorrect (correct properties, accessible resources...). The licecyel controller impacts the instance lifecycle, if you want to impact only the registered service, have a look to the service controller (<a href="/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/providing-osgi-services.html">service providing</a>.</em></p>
<div class="toc">
<ul>
<li><a href="#lifecycle-controller-handler">Lifecycle Controller Handler</a><ul>
@@ -219,7 +219,7 @@
may be trademarks or registered trademarks of their respective owners.
</div>
<div class="timestamp span3 offset2">
- Rev. 1443561 by clement on Thu, 7 Feb 2013 15:37:01 +0000
+ Rev. 1475720 by clement on Thu, 25 Apr 2013 12:13:11 +0000
</div>
</div>
</footer>
Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/providing-osgi-services.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/providing-osgi-services.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/providing-osgi-services.html Thu Apr 25 12:13:25 2013
@@ -212,7 +212,7 @@
<p><img src="ps-foo.png"></p>
-<p>The <code><provides/></code> or <code>@Provides</code> suffice to declare that each instance of this type will provide the FooService (for more info about instances see <a href="">FELIX:How-to use iPOJO factories</a>). The provided specifications can be discovered by analyzing the implementation class. By default, all implemented interface are published in the same service registration. iPOJO looks down the entire inheritance tree.</p>
+<p>The <code><provides/></code> or <code>@Provides</code> suffice to declare that each instance of this type will provide the FooService (for more info about instances see '<a href="/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/ipojo-advanced-topics/how-to-use-ipojo-factories.html">How to use iPOJO factories</a>`). The provided specifications can be discovered by analyzing the implementation class. By default, all implemented interface are published in the same service registration. iPOJO looks down the entire inheritance tree.</p>
<h2 id="service-publication">Service Publication</h2>
<p>The provided service handler manages service publication. For each declared <code><provides/></code>, the handler registers a service. Since the <code>@Provides</code> annotation can be used only once, only one service is registered that provides all interfaces. The service is published as long as the instance is valid. If the instance becomes invalid, the service is removed from the service registry.</p>
<p>By default, it publishes all interfaces implemented by the implementation class of the component class. It collects all super-interfaces (interfaces implemented by implemented interfaces and by the super class). However, it is possible to explicitly declare which service specifications are published with the <code>specifications</code> attribute, such as:</p>
@@ -545,7 +545,7 @@
may be trademarks or registered trademarks of their respective owners.
</div>
<div class="timestamp span3 offset2">
- Rev. 1444686 by clement on Mon, 11 Feb 2013 09:16:09 +0000
+ Rev. 1475720 by clement on Thu, 25 Apr 2013 12:13:11 +0000
</div>
</div>
</footer>
Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/developing-camel-mediators-with-ipojo.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/developing-camel-mediators-with-ipojo.html (original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/developing-camel-mediators-with-ipojo.html Thu Apr 25 12:13:25 2013
@@ -159,7 +159,7 @@
<div class="container">
<div class="content">
<h1 id="developing-camel-mediators-with-ipojo">Developing Camel mediators with iPOJO</h1>
-<p><em>The <a href="http://http://camel.apache.org/tutorial-osgi-camel-part1.html">Camel OSGi tutorial </a> provides a very simple and neat overview of Camel. This article mentions the usage of iPOJO to implement the mediator. This document provides this implementation.</em></p>
+<p><em>The <a href="http://camel.apache.org/tutorial-osgi-camel-part1.html">Camel OSGi tutorial </a> provides a very simple and neat overview of Camel. This article mentions the usage of iPOJO to implement the mediator. This document provides this implementation.</em></p>
<h2 id="step-1-initial-project-setup">Step 1 : Initial project setup</h2>
<p>Instead of using the 'spring-osgi-bundle-archetype' maven archetype, we will use the iPOJO one to create the iPOJO bundle.
To create the simple iPOJO service project, execute the following command in your Unix/Dos console.</p>
@@ -320,7 +320,7 @@ Create or edit the file <code>metadata.x
may be trademarks or registered trademarks of their respective owners.
</div>
<div class="timestamp span3 offset2">
- Rev. 1475684 by clement on Thu, 25 Apr 2013 09:35:53 +0000
+ Rev. 1475720 by clement on Thu, 25 Apr 2013 12:13:11 +0000
</div>
</div>
</footer>