Hi again,
It is indeed the same issue described by Amichai.
As a workaround, I reverted org.apache.felix.fileinstall to 3.6.4.
To achieve that I used the featuresProcessing mechanism to replace the
original bundle. As a side note. I don't know who was the person or persons
responsible for the featuresProcessing feature, but many, many thanks. This
is a great feature.
For anyone that faces the same issue, this is what I have done.
* Specified the featuresProcessing parameter in karaf-maven-plugin
configuration:
<featuresProcessing>${project.basedir}/features-processing.xml</featuresProcessing>
The value is an XML file with the following contents
<?xml version="1.0" encoding="UTF-8"?>
> <featuresProcessing xmlns="
> http://karaf.apache.org/xmlns/features-processing/v1.0.0"; xmlns:f="
> http://karaf.apache.org/xmlns/features/v1.6.0";>
>
> <bundleReplacements>
> <bundle
> originalUri="mvn:org.apache.felix/org.apache.felix.fileinstall/3.6.6"
> replacement="mvn:org.apache.felix/org.apache.felix.fileinstall/3.6.4"
> mode="maven" />
> </bundleReplacements>
>
> </featuresProcessing>
>
Thank you,
João Assunção
Email: [email protected]
Mobile: +351 916968984
Phone: +351 211933149
Web: www.exploitsys.com
On Fri, Jul 10, 2020 at 5:30 AM Jean-Baptiste Onofre <[email protected]>
wrote:
> Hi,
>
> It’s not directly a Karaf issue: we have a Jira at Felix FileInstall. I
> will fix that and release a new Felix FileInstall version.
>
> Regards
> JB
>
> Le 9 juil. 2020 à 21:55, João Assunção <[email protected]> a
> écrit :
>
> Hello all,
>
> I use the config element in feature.xml to create configurations for my DS
> components. Some of these components are factories.
> When I install the feature, the configurations are created, the components
> are activated but then they are deactivated automatically.
> In the logs, I noticed that configurations are created bounded to null,
> but then ConfigAdmin will change the binding to felix.fileinstall. When
> this happens, the associated component is deactivated. This seems to happen
> only for factories and only if I use the feature:install command. If I
> change the feature to boot, this issue doesn't happen.
>
> My factory configurations are specified like this:
> <config name="PID-alias">
> ...
> </config>
>
> I'm running a custom distro based on Karaf 4.2.9
>
> Did anyone experience something similar?
> Thank you,
>
> Best regards,
> João
>
> Email: [email protected]
> Mobile: +351 916968984
> Phone: +351 211933149
> Web: www.exploitsys.com
>
>
>
>
