As a plugin developer or system admin I can deploy OSGI bundles into the Liferay portal

• Type: Story
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: 6.2.0 CE M4
• Component/s: Tools, Tools > Plugins SDK > Web
• Labels: None
• Epic/Theme:
  • Modularity
  • Platform
• Similar Issues: Show 5 results ; ;

  LPS-26268	Automatically convert Liferay plugins into OSGi bundles when they are deployed
  LPS-32502	As a Portal Administrator I can manage (view, start, stop, install, ...) all the OSGI bundles installed through an administration UI
  LPS-34424	Extract all the OSGi related stuff from the Liferay core to the plugins SDK
  LPS-32184	As a plugin developer I can easily specify which OSGi services are needed or exported by a plugin/bundle in a declarative way
  LPS-19662	Turn Liferay libraries into OSGi bundles

The main benefit for system administrators is:

• Get a whole lifecycle of their applications regardless of the App Server container: start, stop, uninstall, . . . are some of the available operations. This lifecycle management is independent of the application server being used, which means that it will be available in all app servers supported by Liferay.

Plugin developers get the following benefits:

• Use Liferay services as OSGI services, which means that the OSGI takes care of all the necessary classloader handling.
• Dependency management: if is possible to divide a certain functionality in several components and declare dependencies. When deploying the modules, Liferay (through the OSGi container) will ensure the dependencies are met or else the bundle is kept on hold until they are.
• Make plugins extensible (through other plugins) in a much easier way.
• Develop a service and make it easily available to many plugins. This is a typical need of portlet developers who have to split the portlets in several plugins.

All this is achieved by having and embedded OSGI runtime within Liferay. An additional benefit for Liferay is that the OSGi container takes care of classloading handling so that it's not necessarily to do it manually in Liferay's code.