Re: Blueprint issue with generics

Again, I'm really not sure that would be a good idea. Some use cases are really useful when actually leveraging parameterized types and conversions. For example, you can have: 3 5 With public class MyBean { public MyBean(List values) { } } If

RE: Blueprint issue with generics

Yep… or maybe have a flag in order Aries to use either the current generic-aware converter or the non-generic one :) (please please please!) Regards, JP De : Guillaume Nodet [mailto:gno...@apache.org] Envoyé : lundi 26 septembre 2016 18:01 À : user@aries.apache.org Objet : Re: Blueprint issue

Re: Blueprint issue with generics

I checked the code, but that's currently the only way. However, one possibility would be to move those 2 lines into a different blueprint xml file, so that the same file can be included in all your bundles more easily at build time, as blueprint will by default load all OSGI-INF/blueprint/*.xml

RE: Blueprint issue with generics

Hi Guillaume, Yep, did not had time to make a full test on all bundles, but the few bundles with the Blueprint addition I tested start without the “unable to find matching…” errors: So it’s another workaround possibility, thanks! I’m not too

Re: Blueprint issue with generics

Have you been able to try the converter ? 2016-09-23 13:07 GMT+02:00 Guillaume Nodet : > > > 2016-09-23 12:22 GMT+02:00 CLEMENT Jean-Philippe < > jean-philippe.clem...@fr.thalesgroup.com>: > >> Hi Guillaume, >> >> >> >> We do have a lot of classes used in the blueprint which