Hi, yes I would even go further and say it's an expected behavior. so nothing to worry about.
regards, Achim 2015-11-26 14:10 GMT+01:00 Jean-Baptiste Onofré <[email protected]>: > Hi JP, > > I don't think it's related to blueprint. > > It's more the way a ManagedService works. > > First the activator starts, and then it will react to the ManagedService > via the update() method. > > I guess it's what you see there. > > Regards > JB > > > On 11/26/2015 02:04 PM, CLEMENT Jean-Philippe wrote: > >> Dear Karaf Team, >> >> I have a strange behavior with Karaf (*) when started for the first >> time. A bean is started then stopped then re-started. This behavior is >> not 100% reproducible but happens maybe one-half of the time. >> >> That bean is instantiated via Blueprint and uses a property-placeholder >> with update-strategy=”reload”. The “Karaf distribution” is made by a >> custom assembly which includes both bundles and configuration files. >> >> During the first bundle start the only configuration variable (a String) >> is not substituted which is a first issue (1). Then the bundle is >> stopped and restarted with the substituted string. This is a second >> issue (2) as I expected the bundle to start only one time as the >> configuration file did not really change. >> >> Is this problem already known? Is there a workaround? >> >> Kind regards, >> >> JP >> >> [@@ OPEN @@] >> >> > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com > -- Apache Member Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead blog <http://notizblog.nierbeck.de/> Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS> Software Architect / Project Manager / Scrum Master
