While this is not going to be a high impact issue in my environment, in my opinion this is an issue for two reasons
1. Karaf is starting up with an obsolete configuration . I can understand Karaf not able to pick up change in file while it is down. But when it starts, it should be able to pick up the change in configuration rather than using a configuration that is no more valid. 2. When I use property place holders with database credentials in a properties file, this issue doesn’t seem to occur. So the behavior no consistent. From: Achim Nierbeck [mailto:[email protected]] Sent: Monday, August 11, 2014 3:11 PM To: [email protected]<mailto:[email protected]> Subject: Re: Data source xml change not taking effect in first karaf start post modification See my comments inline regards, Achim 2014-08-11 11:35 GMT+02:00 <[email protected]<mailto:[email protected]>>: Database parameters are directly mentioned in the blueprint. If I cleanup data folder and start Karaf, latest configuration is considered. Like Achim mentioned, the issue happens when the XML is modified while Karaf is down. Isn’t that a problem ? No I don't think it is really an issue, as the FileInstaller monitors the files it already installed. But if you change it while Karaf is down it usually isn't capable of doing so. Another way would be to install the xml file via maven. Then either update it via osgi:update mvn-coordinates or a bundle:watch (used to be dev:watch in 2.x) The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com
