OK - thanks, /Bengt
2010/9/8 Timothy Ward <[email protected]> > > > Hi Bengt, > > As with many of the Aries projects, we're working to extend standards or > introduce new ones where we feel there are current gaps. An "Application" > concept doesn't really exist in OSGi, but the Aries application work will be > fed back into the OSGi standardisation process. We certainly hope to see a > number of Aries technologies (or something very similar) standardised over > the next OSGi releases. > > Regards, > > Tim > > ________________________________ > > Date: Wed, 8 Sep 2010 09:07:51 +0200 > > Subject: Re: Blueprint and annotations > > From: [email protected] > > To: [email protected]; [email protected] > > > > Justin, > > > > Yes, I agree, many options is a good thing. I'm just trying to get some > > overview on things to make it possible to decide on a direction. > > > > I'm a bit surprised, though, that the OSGi Alliance hasn't standardised > > the annotations - it would make sense I think. But I guess a viable > > path is to use blueprint (XML or annotations) to publish services and > > then use iPojo to consume them? > > > > I'm also evaluating the concept of an Aries application vs Karaf > > features. Seems like a similar concept to me. Is this Aries specific of > > OSGi standard? > > > > /Bengt > > > > > > 2010/9/7 Justin Edelson > >> > > On 9/7/10 11:32 AM, Bengt Rodehav wrote: > >> Justin, > >> > >> Yes I did actually see this but was unsure of its status. Is the > >> annotations specified by OSGi or are they specific to Aries? I'm > >> guessing the former which makes it interesting for portability reasons. > > The Blueprint spec only covers XML. I would hope that the OSGi alliance > > standardizes annotations. > > > >> > >> Functionality wise it is very similar to iPojo. However, iPojo does not > >> seem related to blueprint at all (I might be wrong here) but seems to > >> solve the same problem. iPojo, however, has a lot more functionality and > >> also seems to be more mature. > > You are free to use iPojo and Blueprint within the same application. > > This is, to me, one of the best parts about OSGi - how a service is > > published has no bearing on how it is consumed. > > > >> > >> Have you had any contact with Clement Escoffier at the Felix/iPojo > >> project? Seems like iPojo would be a natural candidate for the blueprint > >> annotation functionality. I'm a bit confused as to what path I should > >> choose and also why there are two different paths regarding this within > >> Apache. > > There's more than 2 within Apache. :) > > > > There's also an implementation of the Declarative Services spec in the > > Felix project (Felix SCR). The Felix SCR Maven plugin supports > > annotations at compile time to produce the DS descriptor file. > > > > Justin > > > >> > >> Do you have more information on this matter? > >> > >> Also, what is the status of Aries blueprint annotation support? Is it > >> being used in production? When will it be released? > >> > >> /Bengt > >> > >> > >> > >> 2010/9/7 Justin Edelson > > > >>>> > >> > >> Did you see http://incubator.apache.org/aries/blueprintannotation.html > >> > >> On 9/7/10 2:57 AM, Bengt Rodehav wrote: > >>> Is it possible to publish and consume blueprint services using > >>> annotations? I've been using iPojo in Karaf before which has > > been very > >>> convenient. > >>> > >>> /Bengt > >> > >> > > > > > >
