OSGi

JOnAS 5 integration

Introduction

The key aspect of the integration of JOnAS with Petals will be the new OSGi based services architecture.

  • The first step: JOnAS needs to provide a JBI container, to achieve this goal, Petals should be packaged as a JOnAS service within an (or several) OSGi bundle. This is what is decribed below.
  • Second step (more long term): Petals may also be considered as a set of basic services, some of them relying on some resources provided by JOnAS, so why not decomposing Petals into a set of OSGi bundles, some of them, like the JORAM one, may be common with JOnAS; this way, JOnAS becomes not only a Java EE platform, but a multi-purpose platform, including a JBI infrastructure.
We will first focus on the first step, including some management aspects, i.e. accessing to some Petals management features from JONAS management console and from JASMINe.

Providing Petals as a OSGi bundle

  • JOnAS 5 is based on OSGi, each service is delivered as a bundle. For integrating Petals into JOnAS, it has to be delivered as a OSGi bundle too.

Administration from jonasAdmin

  • JORAM-like : jonasAdmin console contains a joramPlatform node which allows to walk through the JORAM network. It would be interesting to have a similar node for petals (petalsPlatform) enabling to browse the different petals nodes and their content.

Administration from JASMINe

  • JASMINe is an administration tool for SOA platform. The petals support is planned and the work will start by the end of march.

Providing specific/extra annotations for accessing to the JBI resources (connectors, services)

  • Java EE provides annotations for simplifying the application development. The set of standards annotations could be extended for permitting to connect the J2EE application with the JBI objects.