The OSGi Alliance wants 'the community to try out implementations of its specifications'
JAXenter: In which way will OSGi influence future versions of Java EE?
Mike Keith: The last release of Java EE was the beginning of a new direction for Java EE on its way to becoming more modularly architected. This can partly be attributed to OSGi, but also simply because of the direction of Java and the pursuit of more modular architecture and design. Regardless of the source, the principles of modularity are getting incorporated into Java EE and will become more apparent in future releases.
JAXenter: OSGi has recently proposed two new projects: Aries and Gemini. Apache Incubator Project Aries aims to provide an open collaborative forum to evolve the enterprise OSGi application programming model – do you feel that community collaboration is something that has previously been sorely missing from OSGi?
Mike Keith: The OSGi Alliance is fairly typical as a standards body in that it is composed of a group of companies that come together and create technical specifications. While the resulting specifications are open and available, the Alliance is not in the business of hosting public solutions. However, it does have an interest in wanting the community to try out implementations of its specifications. This is the role of open source projects like Gemini and Aries.
JAXenter: Project Gemini hosts many of the OSGi Reference Implementations that showcase EEG specifications – how do you envision Gemini being used in the development of OSGi-based applications?
Mike Keith: The Gemini project is hosted at Eclipse, so first and foremost it can be used by other projects in the Eclipse ecosystem. However, the modules can be picked up and used by anybody that is considering writing an application using OSGi and well-known Java EE technologies. They can be used together or separately, as required.
Mike Keith will present sessions at both JAX London and the co-hosted OSGi Devcon. Full details are available at the JAX London website.