developerWorks: Leave Eclipse Plug-In Headaches Behind with OSGi

[ Thanks to An Anonymous Reader for
this link. ]

“This article shows an example of one plug-in taking in XML to
register extensions for a defined extension point. We accomplish
this complete decoupling of components by having the plug-ins
Extension Registry aware and providing an OSGi service.

“As you know, Eclipse’s component architecture is
plug-in-based–meaning that a bunch of code is componentized into a
single component, then registered with the Eclipse framework as one
of its components others can then bind to or call into. Extension
points are ways for plug-ins to allow for others to contribute
additional functionality to the plug-in exposing the extension
point. Now take all of that and wrap it up into a controlled
runtime where plug-ins can come and go dynamically, and you get
OSGi (basically)…”

Complete Story