Skip to main content

Using Equinox CommandProvider to make OSGi console interactive.

After fiddling with the First Bundles that "Hello World"-ed upon Activation, You want to see more interactivity in OSGi. Although Using OSGi for an interactive Command Line Application would be like this one would be, well, a callable over-kill, I am going to start with an example and Expand it in later posts. So, please Welcome CommandProvider.

CommandProvider is an EQUINOX specific API for extending the Console. This basic Example illustrates how to get a command from console and do something in java and also gets your feet wet on Service Registry
package com.so.examples.commandconsole;

import org.eclipse.osgi.framework.console.CommandInterpreter;
import org.eclipse.osgi.framework.console.CommandProvider;

public class DisplayMessageCommand implements CommandProvider {

 public void _say(CommandInterpreter ci) {
  ci.print("You said:" + ci.nextArgument());
 }

 @Override
 public String getHelp() {
  return "\tsay - repeats what you say\n";
 }

}

This provider class implements CommandProvider, which is actually just a marker interface, except that getHelp is a helper to print out additional help data when user types in help. The actual commands follow the java reflection pattern as a method that starts with an underscore(_), takes CommandInterpeter as parameter and returns void. So there can be more than one command provided by one CommandProvider Class. Important thing here is, this could have been easily(, better) achieved with annotations, but OSGi inherently is for ALL java platforms, so its implemented this way.

Next step is to tell the framework to commands from this CommandProvider. To do that, We have to "bind" this to framework as a service. You could do it anytime you have access to the bundle context, but the easiest place is when starting the bundle. An Activator like the one below should do.
public class CommandBundleActivator implements BundleActivator {

 @Override
 public void start(BundleContext context) throws Exception {
  context.registerService(CommandProvider.class.getName(),
    new DisplayMessageCommand(), null);

 }
//stripped ...

Notice that we are using equinox specific packages, so in our manifest, we add, along with the Activator
Bundle-Activator: com.so.examples.commandconsole.CommandBundleActivator
Import-Package: org.osgi.framework,
 org.eclipse.osgi.framework.console

What happens under the hood: Equinox when started with -console parameter, starts the framework also initiating a default CommandProvider Service Implementation (ignoring -console will not start the console, hence exitting back to shell). Which is the one that accepts the commands and performs actions. And EQUINOX, provides a way to extend it by adding other Implementations of CommandProvider to the ServiceRegistry.

Now start up the framework, install the new bundle, and start it,
osgi> help
 say - repeats what you say
---Eclipse Runtime commands---
 diag - Displays unsatisfied constraints for the specified bundle(s).
 enableBundle - enable the specified bundle(s)
#stripped off..
osgi> say Sarath
You said:Sarath

This brings to the next topic, which I will discuss in the next post, The Service Registry. The example project is available here.

Popular posts from this blog

Being a Vegetarian

I am a Proud Vegetarian. I don't eat Meat or Eggs. People say its hard here in US to be one. I beg to differ. The mere fact that I am hail and healthy these 4 years is a definitive proof. Apart from being bullied and trash talked by The Meat-Eaters, There is really nothing that makes this choice of mine any more than a debatable issue at a lunch or dinner. Other things aside, I am writing this blog having watched a PETA Video. Before you click on the play button, I ask you - If you are a vegetarian : Dont watch it. If you are not : Dare to watch it till the end. If you think going veg is just a fashion, think again . Even if you just want to do it for Fashion . Do it. Go Vegetarian. And Feel better asking the waiter for a Vegetarian Entrée in your next lunch.

How to Make a Local (Offline) Repository in Ubuntu / Debian

If you are in a place where you dont have internet (or have a bad one) You want to download .deb packages and install them offline. Each deb file is packaged as a seperate unit but may contain dependencies (recursively). apt-get automagically solves all the dependencies and installs all that are necessary. Manually install deb files one by one resolving each dependency would be tedious. A better approach is to make your own local repository. Before you actually make a repo, You need *all* deb files. You dont practically have to mirror all of the packages from the internet, but enough to resolve all dependencies. Also, You have to make sure, you are getting debs of the correct architecture of your system (i386 etc) # 1. make a dir accessible (atleast by root) sudo mkdir /var/my-local-repo # 2. copy all the deb files to this directory. # 3. make the directory as a sudo dpkg-scanpackages /var/my-local-repo /dev/null > \ /var/my-local-repo/Packages # 4. add the local repo to sour