Gemini Web Feat: Gemini Naming or Injecting OSGi Services the Java EE Way

Session Type: 
Standard [25 minutes]

Schedule info


You want to build dynamic and modular Web Applications and you’ve already chosen OSGi to achieve the modularity. Now you also want to take benefits of using the OSGi services, while still using the standard Java EE way of dependency injection. We’ve got good news for you!

Join this session to learn how you can do all this by leveraging current standard based technologies. In 25 minutes you will learn how to create and build a small Web Application bundle and to consume OSGi services as any other resources. Now it is possible to do this transparently and OSGi knowledge is not required.

If you want to get acquainted with the topic upfront (while not strictly required), you can go though the following materials:
Gemini Web is based on the Reference Implementation of the Web Applications specification from the OSGi Alliance. The Web Application specification describes in details how:

  • Web Applications written according to the Java Servlet and JSP specifications will be supported in OSGi
  • Web Application packaged as a WAR can be installed into an OSGi based runtime, and how it can integrate with OSGi services
  • An OSGi bundle can provide web content managed using the Java Servlet specification, in addition to being managed by OSGi from a bundle lifecycle perspective

Gemini Naming implements support for Java Naming and Directory Interface within an OSGi environment. It provides:

  • Standard mechanism for publishing and locating JNDI Service Provider implementations within an OSGi framework
  • Support for the existing traditional model of JNDI clients
  • New service-based model for interacting with JNDI providers
  • Ability to access OSGi services using OSGi-based URL lookups