Details

      Description

      As explained in the story's description, the new approach tries to bring a few improvements over the current solution.

      The fundamentals of the new approach are:

      • A single @Component will have all the required portal dependencies.
      • Every module will be able to express its own OSGi dependencies using the @ServiceReference annotation and/or the META-INF/spring/context.dependencies file

      Every Spring context will be treated as a single unit, managed by the Dependency Manager framework. This means that we are not using an "active waiting" approach to create the contexts for every Service Builder application but an approach similar to the one used by Declarative Services.

      It is important to highlight that, if any of the dependencies of the Context is gone, the context as a whole will be destroyed. We are not trying to add "dynamism" to the Spring context, but just bridge the two worlds (OSGi and Spring) with a simple and robust solution

        Attachments

          Activity

            People

            Assignee:
            miguel.pastor Miguel Ángel Pastor Olivar (Inactive)
            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, 29 weeks, 6 days ago

                Packages

                Version Package
                7.0.0 M7