As a plugin developer I can easily specify which OSGi services are needed or exported by a plugin/bundle in a declarative way

• Type: Story
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: 7.0.0 M6
• Component/s: Dev Tools, Dev Tools > Plugins SDK
• Labels: None
• Epic/Theme:
  • Modularity
  • Platform

The usual way of using OSGi services from code is to use its API to grab the service (this often requires, extending an interface, implementing some methods, etc). Also, in order to expose a functionality as an OSGi service the OSGi API needs to be used.

OSGi also has an specification known as Blueprint Services which allows avoiding using the API and thus having OSGI specific code within the bundle. Instead the services needed or exposed are specified in an XML file, annotations, ... which is cleaner and easier to use.

In order to achieve this, Liferay will use the Eclipse Gemini (previously known as Spring DS) which allows injecting as well beans declared through Spring (and that's a great thing since Liferay uses Spring beans extensively)