Hi, afaik Pax CDI is using the CDI annotation, and OSGi services are handled transparently and internaly. so for me this doesn't sound like a good idea. But I'll leave that to Guillaume Nodet, as he made sure that Pax CDI is CDI compatible.
regards, Achim 2017-09-25 20:43 GMT+02:00 Dominik Przybysz <[email protected]>: > Hi, > I've checked pax-cdi-api when I was trying to resolve issue > https://issues.apache.org/jira/browse/ARIES-1740 and the annotations that > we are using in the blueprint maven plugin will be not available. > > pax-cdi-api replaced @OsgiService and @OsgiServiceProvider with annotation > @Service which, in my opinion, do not meet our needs. > > The best option is to create own set of annotations, so it will be under > Aries control and we won't depend on someone's changes. > > I propose the annotations (every annotation will have properties > coresponding to the relative attributes): > - @Service > - @ServiceProperty > - @Reference > - @ReferenceList > > The handlers for pax annotations I will move to separate sub module as we > have done for spring handlers. > > What do you think? > > -- > Pozdrawiam / Regards, > Dominik Przybysz > -- Apache Member Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead blog <http://notizblog.nierbeck.de/> Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS> Software Architect / Project Manager / Scrum Master
