[FELIX-4436] DirectoryWatcher should not refresh transformed bundles on every start-up

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: fileinstall-3.2.4
• Fix Version/s: fileinstall-3.4.0
• Component/s: File Install
• Environment: ServiceMix 4.5.3
• Assignee: Guillaume Nodet
• Reporter: metatech
• Created: 26/Feb/14 14:02
• Updated: 17/Mar/15 06:55
• Resolved: 08/Apr/14 14:01

Description

DirectoryWatcher can auto-deploy JAR or XML files placed in a directory.
Blueprint XML files (containing for instance ActiveMQ factories or JAAS realms) are detected as "installed" on every start-up. Prior to FELIX-2066, this had no effect. Since FELIX-2066, bundles detected as "installed" are now forcibly "refreshed" on every start-up. The impact is that these bundles are stopped and restarted during the container start-up. Because there are some race conditions (see FELIX-3067), this can prevent those XML files or other bundles depending on them from fully starting. Here is a patch which avoids restarting those bundles when they were not modified.

Issue Links

• breaks: SMX4-956 Monitor etc/activemq-broker.xml for changes
• relates to: KARAF-2420 blueprint deployer: redeploy untouched blueprint xml in deploy folder after restart