Details

      Description

      The new approach for our Service Builder based applications will allow the end user to define dependencies on regular OSGi services.

      In order to do that, we are putting in place a new mechanism were these dependencies will be handled by the new infrastructure in order to create and destroy the Spring context in a nice manner.

      How does the plugin work?

      • You just need to define in your application which annotation is going to be used to define your Service dependencies. For example, in the portal, we will be writing:
      -service-dependencies: com.liferay.portal.kernel.bean.BeanReference
      

      The previous snippet means that all the beans created within our application contexts which has a field with this annotation will be processed, and this classes will be used as dependencies that will be need to be satisfied before creating the final context

      In addition to that, you will be able to define dependencies in the file

      META-INF/spring/context.dependencies
      

      using the following format

      serviceClass1 [filter]
      serviceClass2 [filter]
      ...
      serviceClassN [filter]
      

      For example, if you want to express a dependency on a service of type bar.foo.Foo you will need to write something like

      bar.foo.Foo (a=1)
      

        Attachments

          Activity

            People

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

              Dates

              Created:
              Updated:
              Resolved:
              Days since last comment:
              6 years, 30 weeks, 1 day ago

                Packages

                Version Package
                7.0.0 M7