You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by Dominik Przybysz <al...@gmail.com> on 2017/09/25 18:43:46 UTC
Pax-cdi-api will change in version 1.0.0
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
Re: Pax-cdi-api will change in version 1.0.0
Posted by Dominik Przybysz <al...@gmail.com>.
Hi,
so we need new annotations. I propose:
- @Service and @ServiceProperty for generating service element in XML
- @Reference for generating reference element
- @ReferenceList for generating reference-list element
What do you think?
2017-09-25 21:20 GMT+02:00 Guillaume Nodet <gn...@apache.org>:
> I'm not sure why pax-cdi annotations have been used in the first place.
> They really have nothing to do with blueprint.
> I think the handler should be marked as deprecated too.
>
> 2017-09-25 20:43 GMT+02:00 Dominik Przybysz <al...@gmail.com>:
>
> > 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
> >
>
>
>
> --
> ------------------------
> Guillaume Nodet
>
--
Pozdrawiam / Regards,
Dominik Przybysz
Re: Pax-cdi-api will change in version 1.0.0
Posted by Guillaume Nodet <gn...@apache.org>.
I'm not sure why pax-cdi annotations have been used in the first place.
They really have nothing to do with blueprint.
I think the handler should be marked as deprecated too.
2017-09-25 20:43 GMT+02:00 Dominik Przybysz <al...@gmail.com>:
> 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
>
--
------------------------
Guillaume Nodet
Re: Pax-cdi-api will change in version 1.0.0
Posted by Achim Nierbeck <bc...@googlemail.com>.
hmm ... I guess I'v jumped to the wrong list :D
you are right so forget about what I said.
Some I was under the impression of you've been talking about changing Pax
CDI back ...
so please never mind :)
2017-09-25 21:04 GMT+02:00 Dominik Przybysz <al...@gmail.com>:
> @Achim
> I've lost the context. What does not sound good for you? Are you writing
> about own annotations set or current changes in pax?
>
> Pax CDI and CDI are not part of Aries. The problem is that generating
> blueprint from annotations depends on pax annotations. It was great at the
> beggining, but now we should not look back on pax.
>
> 2017-09-25 20:49 GMT+02:00 Achim Nierbeck <bc...@googlemail.com>:
>
> > 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 <al...@gmail.com>:
> >
> > > 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
> >
>
>
>
> --
> 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
Re: Pax-cdi-api will change in version 1.0.0
Posted by Dominik Przybysz <al...@gmail.com>.
@Achim
I've lost the context. What does not sound good for you? Are you writing
about own annotations set or current changes in pax?
Pax CDI and CDI are not part of Aries. The problem is that generating
blueprint from annotations depends on pax annotations. It was great at the
beggining, but now we should not look back on pax.
2017-09-25 20:49 GMT+02:00 Achim Nierbeck <bc...@googlemail.com>:
> 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 <al...@gmail.com>:
>
> > 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
>
--
Pozdrawiam / Regards,
Dominik Przybysz
Re: Pax-cdi-api will change in version 1.0.0
Posted by Achim Nierbeck <bc...@googlemail.com>.
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 <al...@gmail.com>:
> 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