Re: https://issues.apache.org/jira/browse/KARAF-4829

Btw, I closed the jira because the initial problem is not a problem per se. When used properly, config files are pushed to ConfigAdmin before bundles are started. This only happen because of the use of those typed properties files which aren't really supported yet. 2017-04-03 19:22 GMT+02:00

Re: https://issues.apache.org/jira/browse/KARAF-4829

You can use a properties file. Afaik, there's no problem with them and they are fully supported. Config files with typed properties will be supported through KARAF-5074 which is a new feature. For the location attribute, a new JIRA would be

https://issues.apache.org/jira/browse/KARAF-4829

Hi, The issue KARAF-4829 was closed. I thought I could now use the config tag as long with a location attribute, but I’m wrong! How to configure a feature in order configuration files to be installed prior to bundle startup? Thanks! Regards, JP De : Guillaume Nodet

Re: Blueprint fails instantiating bean with generic constructor

2017-04-03 17:03 GMT+02:00 CLEMENT Jean-Philippe < jean-philippe.clem...@fr.thalesgroup.com>: > I understand your point and you’re right, it’s better to test things early > than let the system crash later on. To go further I guess the Blueprint > spec would have to be enhanced to fully support

Is there an upgrade process for Karaf 4.1.0 to 4.1.1?

Is there an upgrade process for Karaf 4.1.0 to 4.1.1 or is this a wipe and replace? Mike -- View this message in context: http://karaf.922171.n3.nabble.com/Is-there-an-upgrade-process-for-Karaf-4-1-0-to-4-1-1-tp4050010.html Sent from the Karaf - User mailing list archive at Nabble.com.

RE: Blueprint fails instantiating bean with generic constructor

I understand your point and you’re right, it’s better to test things early than let the system crash later on. To go further I guess the Blueprint spec would have to be enhanced to fully support generics, for instance to be able to instantiate an ArrayList bean, to expose and retrieve services

Re: Blueprint fails instantiating bean with generic constructor

I still am not comfortable allowing casting List to List as we perfectly know what will happen. Blueprint is not a compiler, but if you look at CDI, those kind of problems have been handled correctly for example, and CDI is not a compiler either, but both blueprint and CDI are dependency

RE: Blueprint fails instantiating bean with generic constructor

Hi Guillaume, As already discussed, Blueprint is not a compiler but a runtime library. Once compiled there is no more generics as Java is a type erasure language. Moreover, I’m not too sure how Blueprint may handle injection with things like S getSomething() where in java you can write

Re: Blueprint fails instantiating bean with generic constructor

There are 2 different issues. One is type erasure, i.e. allow the invocation of a method taking a List with a List for example. That's ARIES-1607, and I really think that's a bad idea, unless someone show me a good example where it makes sense. At least by default (well, it's against the

RE: Blueprint fails instantiating bean with generic constructor

Hi JP, Thanks. I've voted it. Regards, Setya -- View this message in context: http://karaf.922171.n3.nabble.com/Blueprint-fails-instantiating-bean-with-generic-constructor-tp4049986p4050004.html Sent from the Karaf - User mailing list archive at Nabble.com.

RE: Blueprint fails instantiating bean with generic constructor

Hi Setya, It might be related to an issue I opened last year: https://issues.apache.org/jira/browse/ARIES-1607 At that time I was told to add a custom converter as a workaround. No update on the Jira since then; maybe you may vote for it :) Regards, JP -Message d'origine- De : Setya

Re: Karaf & feature.xml files

The addUrl command has been renamed to repo-add. So they are the same command. To add a file, you may need to use 3 slashes for a file. The following command works for me: feature:repo-add