Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0
Include Page
FELIX:apache-felix-ipojo-headerFELIX:
apache-felix-ipojo-header

Wiki Markup
{html}
HTML
<div class="content">
{html}

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.

...

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, http://forge.soa4d.org/Image Removed). And it's not just about us: partners of the SOA4D forge are using it, too.

        Sylvain Marie, Software Architect, Schneider Electric

...

JOnAS is a Java EE server developed inside the OW2 consortium. It embraces the new trend of modular and dynamic application servers and aims at implementing the entire Java EE specification by re-using third-part components. JOnAS also focuses on providing a great flexibility for the developer, for the administrator and for clustering.

To enable this flexibility and dynamism in the application server components' integration, the JOnAS team chose to rely on an OSGi runtime. However, it quickly appeared that any manual management of the dynamism would be too expensive: not only very few programmers understand the complexity of the dynamism, but also manual maintaining is extremely difficult and error-prone. That's why JOnAS uses a service-oriented component model.

We first chose iPOJO because this technology sounded really promising. Moreover, iPOJO is able to evolve against new requirements, thanks to the handler-based extensibility model it promotes.

In the JOnAS application server all the technical services are implemented by iPOJO components. Thanks to this framework, they are pluggable and upgradeable on-demand. As iPOJO reduces drastically the impact on the code, we have reused the high majority of our code and the migration from the former JOnAS to this one has been surprisingly quick. The JOnAS team is very happy with iPOJO, and will go on using, promoting and improving it.

If you want more info on JOnAS visit our website.

        Guillaume Sauthier, JOnAS Application Server Developer



Wiki Markup
{html}
HTML
<div class="box">
	<div class="box-blue-header">
	<div class="box-blue-title">
		<img src="http://people.apache.org/~clement/ipojo/site/information.gif"> <b>Are you also using iPOJO ?</b>
	</div>
	</div>
	<div class="box-blue-content">
You are using iPOJO, and you want to be listed there to tell how you are using iPOJO. Feel free to send us <a href="mailto:clement@apache.org">a mail</a> with your story.
	</div>
	<div class="box-blue-footer"></div>
</div>
{html}


Include Page
FELIX:apache-felix-ipojo-footerFELIX:
apache-felix-ipojo-footer