Jump to: navigation, search

Difference between revisions of "OSGI component support in Service Creation"

Line 77: Line 77:
  *Setup breakpoint from java source editor
  *Setup breakpoint from java source editor
  *Deploy to osgi server as mentioned above
  *Deploy to osgi server as mentioned above
  *Start the osgi server in debug mode.
  *Start the osgi server in debug mode as below.
[[Image:Server view felix.PNG]]

Revision as of 03:46, 27 December 2007

This wiki is aiming to discuss how to support OSGI based service component development in STP. Johnson Ma, Dec 27, 2007


As more and more Middleware servers becomes OSGI based. We need to support users to create service component in the format of OSGI bundle in an Service Oriented Approach.

We will use ServiceMix 4.0 as a reference SOA runtime here, which is based on Apache Felix OSGI implementation.

Existing OSGI tooling

PDE OSGI tooling support

"Eclipse PDE UI also provides comprehensive OSGi tooling, which makes it an ideal environment for component programming, not just Eclipse plug-in development."

Apache Felix integration with Eclipse

Felix integration with eclipse from felix site, is a solution to integrate Felix with Eclipse IDE by

*Check out felix projects into Eclipse workspace
*Add the felix.jar to java project's classpath
*Create java launch config to run org.apache.felix.main

Spring OSGI Eclipse integration

How to create a Spring OSGI bundle proejct in Eclipse

Setting up Eclipse for Spring Dynamic Modules development

Requirements for OSGI tooling from Service Creation point for view

*Replaceable OSGI runtime:Should define extension point to locate osgi runtime
*Easy dependency configuration::Help user to setup dependencies to existing bundle/service loaded in the runtime
*Manifest Editor: user friendly manifest editor following OSGI spec. Try to reuse the Manifest editor from PDE here.
*Run and Debug support::  
*OSGI Console support: should show the osgi console in eclipse 

How to create a OSGI service component

How to deploy OSGI component to runtime

There maybe two ways for the deployment:

  • Extending the WTP server framework for osgi runtime
  • or extending the PDE osgi.frameworks

I prefer the WTP based solution. since it can be better integrated with SOAS in stp.

Deploy to WTP server

*Define a WTP server extension for OSGI runtime (ServiceMix for example)
*Users can start/stop the runtime from WTP server view
*Deploy user created osgi bundle to the server

Deploy using PDE?

org.eclipse.pde.ui.osgiFrameworks extension

Create a new osgi framework extension. The following example will create a new Apache Felix OSGI framework in eclipse

           name="Felix OSGI Framework">


Preference for OSGI Framework

Windows->Preference->Plugin Development->OSGI Framworks will list all supported runtime. You can see the Apache Felix OSGI implementation we just added

Osgi framework preference.PNG

OSGI Framework launch configuration

Create launch configuration under Run>OSGI framework.

Run apache felix.PNG

How to test and debug

Users can follow steps below to debug the osgi component:

*Setup breakpoint from java source editor
*Deploy to osgi server as mentioned above
*Start the osgi server in debug mode as below.

Server view felix.PNG

OSGI Console in eclipse

Since we start ServiceMix using WTP server framework. The OSGI console should show in the console view in Eclipse. Thus users can send commands, such as ss, start, stop, shutdown...etc.

User Scenarios

Spring meta data editor

The ServiceMix runtime is based on the Spring framework. We should looking into how to help users to create spring configuration --- a Spring metadata editor. (reuse editor from SpringIDE?)