[forge-dev] forge on osgi
paul.bakker.nl at gmail.com
Fri Jun 17 08:28:13 EDT 2011
Since I started to work with OSGI a lot recently I start to feel more and
more that Forge should run on OSGI. We have discussed this before but I now
have a more clear view of how to do that.
How I would like to structure it:
-The shell becomes the most important bundle. In the bundle activator we
-Every plugin (including all internal ones) become OSGI services in separate
bundles (this will hardly require any code changes)
-We deploy all bundles in an OSGI runtime (e.g. Felix) and start up from
When the shell needs to execute a plugin, or need to create a list of
plugins it uses the BundleContext to retrieve all services that publish the
Plugin interface (which is currently already a marker interface). We iterate
over the list of services and check the @Alias annotation to know which
plugins are there.
After the plugin has been found we can iterate over all methods to find all
The service lookup mechanism can probably even be done in a nicer way by
using https://github.com/mathieuancelin/weld-osgi which looks excellent.
For plugins, everything will stay the same, we can still inject the Shell
etc, the only thing is that we actually inject services under the hood. It
will require a significant rewrite at the core, but I think it's do-able and
will avoid a lot of difficult problems later on. The largest problem at the
moment that I still worry about is that plugins are not really isolated from
the core at the moment, which makes it impossible for plugins to use
additional libraries for example. The maven build and project structure
won't have to change.
If we do this, it will give us a nice way to solve the plugin repository
problem too. We can use the existing bundle repository spec. for this which
includes transitive dependencies etc.
Just to demonstrate my idea I uploaded a very, very, simple prototype. This
uses bndtools which should be replaced by weld-osgi, but the code is pretty
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the forge-dev