Update 21th July 2009

• Version 1.2.1 released
• FIXED BUG: Wrong Guice version in runtime zip

Update 14th July 2009

• Version 1.2 released
• Update to latest Pax bundles
• Minor fixes in DirInstaller
• Removed profiles to improve the startup performance
• The runtime zip is now self-contained

Update 27th March 2009

• ModuleFusion won the Eclipse Community Award in the category "Best Open Source Equinox Application"

Update 22th December 2008

• New version 1.1.0
• ModuleFusion is now based on Pax Runner
• Distribution now is split into a core "runtime" and "feature packs" modules
• Fixed  issue 5 
• Added OSGi Declarative Services
• Added Pax URL
• Added Pax Logging
• Added JSP support
• Added Apache Felix - OSGi Bundle Repository support

Update 6th October 2008

• ModuleFusion's build is now available (see http://code.google.com/p/modulefusion/wiki/BuildModuleFusion)

Update 19th September 2008

• Separated start and debug scripts
• Added Windows startup files start.bat / debug.bat
• New version: 1.0.2

Update 18th September 2008

• Fixed  issue 1 : Dirinstaller start fails because of UnsupportedClassVersionError
• New version: 1.0.1

A lot of momentum exists to use the OSGi Service Platform for the foundation and runtime platform for enterprise Java applications. Well-known vendors in the JavaEE space are building their work on top of the OSGi framework. Additionally, more and more projects and technologies are using the OSGi programming model and component architecture. Bundles are becoming the universal deployment artifact and the service registry is used for SOA, web services and even event-based communication.

The goal of ModuleFusion is to help programmers to use the OSGi Service Platform as their underlying runtime environment. ModuleFusion contains a full stack typical for Java enterprise applications. This stack currently consists of best-of-breed open source frameworks from the Java ecosystem. Additionally, ModuleFusion contains the necessary glue code to easily use these frameworks within OSGi.

Probably the most important principle of ModuleFusion is to base every integration, glue code and additional functionality on pure OSGi constructs. Therefore, ModuleFusion does not rely on proprietary features offered by some OSGi framework implementations.

Also, ModuleFusion shows that it is possible to build full-fledged Java enterprise applications with OSGi now.

Click here to get started!

The Content:

• OSGi Service Platform
• OSGi Framework (Equinox or Felix)
• Configuration Admin
• Event Admin

• Frameworks
• Google Guice IoC framework
• Apache Wicket
• Hibernate
• Hibernate JPA frontend
• Jetty web server
• HSQLDB database
• PAX web + extender bundle

• ModuleFusion
• DirInstaller (install/update/remove bundles and configurations)
• JPA integration
• Apache Wicket integration
• Web Console

• Logging
• Pax Logging