[
https://issues.apache.org/jira/browse/KARAF-4158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15683188#comment-15683188
]
Jean-Philippe CLEMENT edited comment on KARAF-4158 at 11/21/16 10:52 AM:
-------------------------------------------------------------------------
Still there is a first startup issue, at least with config files - for instance:
<feature name="some-feature">
<bundle>mvn:com.whatever/sample/1.0.0</bundle>
<configfile
finalname="/etc/com.whatever.sample.cfg">mvn:com.whatever/sample/1.0.0/cfg</configfile>
</feature>
Where "sample" bundle reads the .cfg file using a property-placeholder. My
assumption is that all .cfg files must be installed (in /etc ...) before
bundles start (which might not be the case on the very first startup) - is it
correct? Else, how to ensure configfiles to be written before the actual
bundles startup?
PS: I did not find where to set the prerequisite="true" option
was (Author: jeanphi):
Still there is a first startup issue, at least with config files - for instance:
<feature name="some-feature">
<bundle>mvn:com.whatever/sample/1.0.0</bundle>
<configfile
finalname="/etc/com.whatever.sample.cfg">mvn:com.whatever/sample/1.0.0/cfg</configfile>
</feature>
Where "sample" bundle reads the .cfg file using a property-placeholder. My
assumption is that all .cfg files must be installed (in /etc ...) before
bundles start, which might not be the case on the very first startup - is it
correct? Else, how to ensure configfiles to be written before the actual
bundles startup?
PS: I did not find where to set the prerequisite="true" option
> Unexpected behavior on first startup
> ------------------------------------
>
> Key: KARAF-4158
> URL: https://issues.apache.org/jira/browse/KARAF-4158
> Project: Karaf
> Issue Type: Bug
> Components: karaf-core
> Affects Versions: 4.0.3
> Environment: RHEL 6.2 x32, Java 1.8.0_72-ea-b05
> Reporter: Jean-Philippe CLEMENT
> Assignee: Christian Schneider
> Fix For: 4.1.0
>
>
> This problem only occurs on the very first startup of a custom assembly. This
> means unpacking the assembly .tar.gz then run karaf. This issue is not 100%
> reproducible. Several untar/run might be necessary to reproduce the issue.
> The problem comes with Blueprint property-placeholders. User bundles might be
> started and not get .cfg replaced properties but the "$(PARAM_NAME)" itself
> (String property).
> I suspect user bundles to be started before the .cfg files are populated in
> the /etc directory.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
