You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@felix.apache.org by cl...@apache.org on 2013/02/11 14:45:07 UTC

svn commit: r1444764 - in /felix/site/trunk/content/documentation/subprojects: ./ apache-felix-ipojo/ apache-felix-ipojo/apache-felix-ipojo-devguide/

Author: clement
Date: Mon Feb 11 13:45:07 2013
New Revision: 1444764

URL: http://svn.apache.org/r1444764
Log:
fix some links

Modified:
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-devguide/dive-into-the-ipojo-manipulation-depths.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-successstories.mdtext

Modified: felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo.mdtext
URL: http://svn.apache.org/viewvc/felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo.mdtext?rev=1444764&r1=1444763&r2=1444764&view=diff
==============================================================================
--- felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo.mdtext (original)
+++ felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo.mdtext Mon Feb 11 13:45:07 2013
@@ -42,31 +42,31 @@ Title: Apache Felix iPOJO
 		<div class="span4 box info">
 			<h4>Why choose iPOJO</h4>
 			<ul class="icons"> 
-			<li><i class="icon-chevron-right"></i> <a href="apache-felix-ipojo-successstories.html#apache-felix-ipojo-successstories-schneider">iPOJO at Schneider Electric</a></li>
-			<li><i class="icon-chevron-right"></i> <a href="apache-felix-ipojo-successstories.html#apache-felix-ipojo-successstories-ugasp">iPOJO at Ubidreams</a> </li>
-			<li><i class="icon-chevron-right"></i> <a href="apache-felix-ipojo-successstories.html" title="apache-felix-ipojo-successstories">others success stories</a></li>
-			<li><i class="icon-chevron-right"></i> <a href="apache-felix-ipojo-keypoints.html" title="apache-felix-ipojo-keypoints">iPOJO Key points</a></li> 
-			<li><i class="icon-chevron-right"></i> <a href="apache-felix-ipojo-why-choose-ipojo.html" title="apache-felix-ipojo-why-choose-ipojo">Why choose iPOJO </a></li>
+			<li><i class="icon-chevron-right"></i> <a href="/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-successstories.html#schneider">iPOJO at Schneider Electric</a></li>
+			<li><i class="icon-chevron-right"></i> <a href="/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-successstories.html#ugasp">iPOJO at Ubidreams</a> </li>
+			<li><i class="icon-chevron-right"></i> <a href="/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-successstories.html" title="apache-felix-ipojo-successstories">others success stories</a></li>
+			<li><i class="icon-chevron-right"></i> <a href="/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-keypoints.html" title="apache-felix-ipojo-keypoints">iPOJO Key points</a></li> 
+			<li><i class="icon-chevron-right"></i> <a href="/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-why-choose-ipojo.html" title="apache-felix-ipojo-why-choose-ipojo">Why choose iPOJO </a></li>
 		</ul>
 	</div> 					
 	<div class="span4 box info">
 		<h4>Getting started</h4>
 		<ul class="icons">
-			<li><i class="icon-chevron-right"></i> <a href="download.html" title="Download">Downloads</a></li>
-			<li><i class="icon-chevron-right"></i> <a href="ipojo-in-10-minutes.html" title="iPOJO in 10 minutes">iPOJO in 10 minutes</a></li>
-			<li><i class="icon-chevron-right"></i> <a href="how-to-use-ipojo-annotations.html" title="How to use iPOJO Annotations">Using Annotations</a></li>
-			<li><i class="icon-chevron-right"></i> <a href="ipojo-hello-word-maven-based-tutorial.html" title="iPOJO Hello Word (Maven-Based) tutorial">Maven tutorial</a></li>
-			<li><i class="icon-chevron-right"></i> <a href="ipojo-support.html" title="ipojo-support">Support</a></li>
+			<li><i class="icon-chevron-right"></i> <a href="http://felix.apache.org/downloads.cgi" title="Download">Downloads</a></li>
+			<li><i class="icon-chevron-right"></i> <a href="/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-gettingstarted/ipojo-in-10-minutes.html" title="iPOJO in 10 minutes">iPOJO in 10 minutes</a></li>
+			<li><i class="icon-chevron-right"></i> <a href="/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-gettingstarted/how-to-use-ipojo-annotations.html" title="How to use iPOJO Annotations">Using Annotations</a></li>
+			<li><i class="icon-chevron-right"></i> <a href="/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-gettingstarted/ipojo-hello-word-maven-based-tutorial.html" title="iPOJO Hello Word (Maven-Based) tutorial">Maven tutorial</a></li>
+			<li><i class="icon-chevron-right"></i> <a href="/documentation/subprojects/apache-felix-ipojo/ipojo-support.html" title="ipojo-support">Support</a></li>
 		</ul>
 	</div>
 	<div class="span4 box info">
 		<h4>The developer corner</h4>
 		<ul class="icons">
-			<li><i class="icon-chevron-right"></i> <a href="describing-components.html" title="Describing components">Describing components</a></li>
-			<li><i class="icon-chevron-right"></i> <a href="ipojo-reference-card.html" title="iPOJO-Reference-Card">iPOJO Reference Card</a></li>
-			<li><i class="icon-chevron-right"></i> <a href="apache-felix-ipojo-eclipse-integration.html" title="apache-felix-ipojo-eclipse-integration">Eclipse Integration</a></li>
-			<li><i class="icon-chevron-right"></i> <a href="apache-felix-ipojo-online-manipulator.html" title="apache-felix-ipojo-online-manipulator">Online Manipulator</a></li>
-			<li><i class="icon-chevron-right"></i> <a href="ipojo-faq.html" title="iPOJO FAQ">FAQ</a></li>
+			<li><i class="icon-chevron-right"></i> <a href="/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components.html" title="Describing components">Describing components</a></li>
+			<li><i class="icon-chevron-right"></i> <a href="/documentation/subprojects/apache-felix-ipojo/ipojo-reference-card.html" title="iPOJO-Reference-Card">iPOJO Reference Card</a></li>
+			<li><i class="icon-chevron-right"></i> <a href="/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-eclipse-integration.html" title="apache-felix-ipojo-eclipse-integration">Eclipse Integration</a></li>
+			<li><i class="icon-chevron-right"></i> <a href="/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-online-manipulator.html" title="apache-felix-ipojo-online-manipulator">Online Manipulator</a></li>
+			<li><i class="icon-chevron-right"></i> <a href="/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/ipojo-faq.html" title="iPOJO FAQ">FAQ</a></li>
 		</ul>
 	</div>				
 </section>

Modified: felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-devguide/dive-into-the-ipojo-manipulation-depths.mdtext
URL: http://svn.apache.org/viewvc/felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-devguide/dive-into-the-ipojo-manipulation-depths.mdtext?rev=1444764&r1=1444763&r2=1444764&view=diff
==============================================================================
--- felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-devguide/dive-into-the-ipojo-manipulation-depths.mdtext (original)
+++ felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-devguide/dive-into-the-ipojo-manipulation-depths.mdtext Mon Feb 11 13:45:07 2013
@@ -18,7 +18,7 @@ The iPOJO byte code manipulation goals a
 
 <img src="process.png">
 
-iPOJO follows a container approach and more specially employs [inversion of control](http://en.wikipedia.org/wiki/Inversion*of*control) and [dependency injections|http://en.wikipedia.org/wiki/Dependency_injection]. The iPOJO container manages component instantiation and injection (service, properties and so on...). To inject values and supervise the execution inside component implementation class, iPOJO uses an interception and injection framework. To facilitate this, iPOJO uses class byte code manipulation. 
+iPOJO follows a container approach and more specially employs [inversion of control](http://en.wikipedia.org/wiki/Inversion_of_control) and [dependency injections|http://en.wikipedia.org/wiki/Dependency_injection]. The iPOJO container manages component instantiation and injection (service, properties and so on...). To inject values and supervise the execution inside component implementation class, iPOJO uses an interception and injection framework. To facilitate this, iPOJO uses class byte code manipulation. 
 
 <img src="injection.png">
 

Modified: felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-successstories.mdtext
URL: http://svn.apache.org/viewvc/felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-successstories.mdtext?rev=1444764&r1=1444763&r2=1444764&view=diff
==============================================================================
--- felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-successstories.mdtext (original)
+++ felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-successstories.mdtext Mon Feb 11 13:45:07 2013
@@ -5,7 +5,7 @@ Title: apache-felix-ipojo-successstories
 # iPOJO Success Stories
 *On this page, you will find comments from industrial users of iPOJO. They come from different domains such as home gateways, mobile phones, or enterprise applications.*
 
-
+<a id="schneider"></a>
 <blockquote>
 Over 90% of processors are now used for embedded applications. At Schneider Electric we believe that java is a fantastic opportunity to develop some of our applications faster and better. OSGi is an excellent way to ensure that developed java software comes with built-in best practices such as reusability, high cohesion, loose coupling, high flexibility and dynamism.But we definitely don't want our anticipation teams to spend more time on OSGi mechanisms than on Energy Management, our core business! iPOJO helps us to develop quickly, by making developing modules as simple as writing plain old java. We also use it for our open source OSGi DPWS Base Driver ('SOA for devices' forge, on <a href="http://forge.soa4d.org/">http://forge.soa4d.org/</a>). And it's not just about us: partners of the SOA4D forge are using it, too.
 </blockquote>
@@ -13,6 +13,7 @@ Over 90% of processors are now used for 
   
 <hr/>  
 
+<a id="ugasp"></a>
 <blockquote>
 Ubiquitous Multi-player games are one of next trends of mobile games. This type of games offers new experience: users interact with the real world and with the virtual world at the same time! So, player actions such as moves, interactions with smart objects or others players impact the virtual part of the game. The state of the virtual games also impacts the possibilities in the physical part of the games. 
 Creating this kind of games requires managing several types of technologies such as embedded devices (mobile phones, PDA, sensors...), smart objects (RFID, environmental sensors...) and network connectivity (GSM, Edge, 3G, Wifi, Bluetooth...). uGasp (Ubiquitous Gaming Services Platform) is a middleware used to execute ubiquitous multi-player games. It provides an abstraction layer hiding the inherent complexity of such games. uGasp is a major evolution of the Gasp framework using a monolithic stack not suitable to embedded devices. To tackle this issue, we adopted a dynamic, modular, extensible and configurable architecture. But in order to speed up the development, uGasp is based on a service -oriented component model offering all the features "for free" and simplifying the development of dynamic applications. uGasp is based on