Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. 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

    Details

      Description

      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)

        Attachments

          Activity

            People

            Assignee:
            miguel.pastor Miguel Ángel Pastor Olivar (Inactive)
            Reporter:
            miguel.pastor Miguel Ángel Pastor Olivar (Inactive)
            Recent user:
            Kiyoshi Lee
            Participants of an Issue:
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Packages

                Version Package
                7.0.0 M6