Hi Toni, hi Tim, thanks for this information :) Your're probably right. This is too much effort for a simple name clash.
Kind regards, Thomas Am Do., 14. Feb. 2019, 12:08 hat Toni Menzel <toni.men...@rebaze.com> geschrieben: > Keep in mind that DS Annotations are compile-time only annotations where > the tooling produces the (relevant) xml spec at build-time. > You of cause can your own annotations and either add the DS annotations > underneath before tooling kicks-in or generate the xml fully yourself. The > benefit of the second approach might be that your annotations can be more > specific than the DS annotations. The downside is that you lose IDE support > like Bndtools (if this is desired). > > Its been one of the things we where looking into some time ago. Direct > aliasing (or even extension) support what be awesome. But you would end up > doing a large mile by yourself. > In your case - you only wanting to go around the name-clash - its probably > way too much. > > Toni Menzel > > *Developer Ergonomist* > rebaze consultancy > Alleestrasse 25 / 30167 Hannover / Germany > M +49 171 6520284 > www.rebaze.com > > rebaze GmbH, Zollstrasse 6, 39114 Hannover, Germany > Managing Director: Toni Menzel > Phone: +49 <+49%2030%2054909582> 171 6520284 / E-Mail: h...@rebaze.com > Registration Court: District Court of Stendal > Registration Number: HRB 17993 > Sales Tax (VAT) Registration Number: DE282233792 > > > > On Thu, Feb 14, 2019 at 11:48 AM Tim Ward via osgi-dev < > osgi-dev@mail.osgi.org> wrote: > >> Hi, >> >> There isn’t any sort of Aliasing for DS annotations. >> >> Best Regards, >> >> Tim >> >> On 14 Feb 2019, at 09:10, Thomas Driessen via osgi-dev < >> osgi-dev@mail.osgi.org> wrote: >> >> Hi, >> >> is there a mechanism in OSGi that allows to alias specific (DS) >> annotations? (Seems to be possible in Spring according to Vaadin) >> >> Currently Vaadin tries to implement an integration for OSGi and there is >> the case where Users will need to annotate the class with OSGi's @Component >> annotation that declares the service to be Vaadin's Component class. So one >> of them would have to be written with the fqcn. >> >> It's just an inconvenience, but if there's a way to work around that this >> would be great :) >> >> Kind regards, >> Thomas >> _______________________________________________ >> OSGi Developer Mail List >> osgi-dev@mail.osgi.org >> https://mail.osgi.org/mailman/listinfo/osgi-dev >> >> >> _______________________________________________ >> OSGi Developer Mail List >> osgi-dev@mail.osgi.org >> https://mail.osgi.org/mailman/listinfo/osgi-dev > >
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev