It provides the generation of service dependencies based on blueprint descriptors (and SCR maybe). Those dependencies should rather be expressed using generic osgi.service dependencies in the bundle manifest headers and this would remove the need for using applications completely. And these headers should be generated by tools such as the felix maven-bundle-plugin (I'm planning to do that in the near future).
2014-05-05 11:04 GMT+02:00 David Bosschaert <[email protected]>: > Just trying to understand this a little better... > > I thought that the application component provided a significant piece > of the subsystems functionality? Maybe I'm wrong. What is it exactly > that the Aries Application bundles do for subsystems? > > Thanks, > > David > > On 15 April 2014 12:08, Guillaume Nodet <[email protected]> wrote: > > The refactoring is done. > > http://svn.apache.org/viewvc?view=revision&revision=1587513 > > Subsystem is now completely independent of applications and blueprint > > (though it will still be leveraged if present). > > > > > > 2014-04-14 21:35 GMT+02:00 Holly Cummins <[email protected] > >: > > > >> If applications aren't using blueprint this analysis of blueprint files > >> won't be providing any useful information, so we should be able to make > >> something in that chain optional without loss of function. Of course, > doing > >> that refactoring may not meet anyone's definition of 'easy'. :) > >> > >> > >> On Monday, April 14, 2014, Guillaume Nodet <[email protected]> wrote: > >>> > >>> Actually, the Aries Application Modeller really needs Aries Blueprint > as > >>> it analyses blueprint files to find provided services, so this > dependency > >>> can't be easily removed. > >>> > >>> Guillaume Nodet > >>> > >>> > >>> 2014-04-14 17:19 GMT+02:00 Guillaume Nodet <[email protected]>: > >>>> > >>>> Yes, it would be nice to have subsystems being independent of > blueprint > >>>> imho. > >>>> > >>>> > >>>> 2014-04-14 16:37 GMT+02:00 Cristiano Gavião <[email protected]>: > >>>> > >>>>> Hi Mark. > >>>>> > >>>>> Well, last time I tried, the subsystems service (zero) wasn't > >>>>> registered without blueprint bundles in active state. > >>>>> Seems that a dependency of subsystem, application-modeller, has a > >>>>> direct dependency to blueprint: > >>>>> > https://github.com/apache/aries/tree/trunk/application/application-modeller/src/main/resources/OSGI-INF/blueprint > >>>>> > >>>>> regards, > >>>>> > >>>>> Cristiano > >>>>> > >>>>> > >>>>> On 11-04-2014 11:45, Mark Nuttall wrote: > >>>>> > >>>>> Hello, > >>>>> I've looked over the code and can only see a dependency on blueprint > in > >>>>> the subsystem-itests pom. So there's a dependency on blueprint to > run the > >>>>> itests, but I cannot see a runtime dependency from subsystem-core on > >>>>> blueprint, Have I missed something? > >>>>> > >>>>> Regards, > >>>>> Mark > >>>>> > >>>>> > >>>>> On 10 April 2014 14:13, Cristiano Gavião <[email protected]> wrote: > >>>>>> > >>>>>> Hi, > >>>>>> > >>>>>> I had a system that was developed using only Declarative Services. > We > >>>>>> are studying to use Subsystem to help with an isolation issue. > >>>>>> > >>>>>> The first problem for us is that it depends on Blueprint and we > don't > >>>>>> like the idea to add this overhead in this environment just to be > able to > >>>>>> use Subsystems. > >>>>>> > >>>>>> Could someone explain me this dependency? are beans being injected > or > >>>>>> just services? > >>>>>> > >>>>>> would be possible to use DS instead of Blueprint in case no bean > being > >>>>>> injected ? > >>>>>> > >>>>>> thanks > >>>>>> > >>>>>> Cristiano > >>>>> > >>>>> > >>>>> > >>>> > >>> > > >
