Thursday, September 24, 2009

Pure Java OSGi demo implementation

To interface with OSGi we need a handle to the BundleContext. OSGi provides for an ‘activator’ that is basically the main() method for when a bundle gets started. To create an activator we will implement the BundleActivator interface. The interface has start and stop methods which are invoked at times that their names suggest and you can control the behavior in your implementing class. Then in the Maven plugin (in the POM) add this instruction:
The shared service: The interface for the shared service is one simple method
String doSomething();
Creating a service implementation: The ComplexService we defined now needs to be implemented and made available as an OSGi service. Here is the Activator:
public class Activator implements BundleActivator{
 public void start(BundleContext context) throws Exception {  
  //register the complex service impl  
    new ComplexService(){
     public String doSomething() {
      return "Hello from Version 1!";
The service is implemented and registered with the bundle context.
Creating the servlet: This is done by implementing the Servlet interface. The ComplexService does something and the response is sent back to the client. The service to be used is chosen at random in this simple example.
public class MyHandler implements Servlet {
 private List<ComplexService> complexServices = new ArrayList<ComplexService>();
 public synchronized void addComplexService(ComplexService service) {
 public synchronized void removeComplexService(ComplexService svc) {
 public void service(ServletRequest request, ServletResponse response)
  throws ServletException, IOException {
  //we may have discovered more than 1 service
  if(complexServices==null|| complexServices.size()==0){
   response.getOutputStream().print("No Service found!");
   //there are 1...n services, pick one
   //using a random pick
     new Random().nextInt(complexServices.size())).doSomething());
Creating the http handler: The Activator for the HTTP Handler must now get a reference to this service and in turn register itself with the HTTP Server.
In addition to the BundleActivator I am also going to implement the ServiceListener interface. This allows us to get event notifications as services start/stop. We want to dynamically support multiple versions of the ComplexService. The Activator looks like this:
public class Activator implements BundleActivator, ServiceListener{
 private MyHandler myHandler;
 private BundleContext bundleContext;
 public void start(BundleContext context) throws Exception {
  //we need this later
  bundleContext = context;
  //we are interested in service updates
  //load referenced services  
  //http service to register handler
  ServiceReference svcRef = context.getServiceReference("org.osgi.service.http.HttpService");
  HttpService httpService = (HttpService)context.getService(svcRef);
  //create and register http handler (catch all)
  myHandler = new MyHandler();  
  httpService.registerServlet("/", myHandler, null, null);
  //get a list of ComplexService (there may be more than 1)
  ServiceReference[] complexSvcRefs = context.getServiceReferences("com.irahul.shared.ComplexService",null);
   for(ServiceReference ref:complexSvcRefs){
  System.err.println("http.handler started!");
 public void serviceChanged(ServiceEvent event) {
  //some service has been registred/removed
  Object svc=bundleContext.getService(event.getServiceReference());
  if(svc instanceof ComplexService){
    System.err.println("New Service added");
    System.err.println("Service stopped");
Next: Running this in Eclipse Equinox

No comments: