[
https://issues.apache.org/jira/browse/FELIX-4436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13934813#comment-13934813
]
Uwe Barthel edited comment on FELIX-4436 at 3/14/14 9:36 AM:
-------------------------------------------------------------
[~metatech]: the patch (pull req. #4) contains the commits of #3 and two new
commits. If it is the 'felix' way, so may I provide a patch file instead of git
pull requests?
was (Author: barthel):
[~metatech]: the patch (pull req. #4) contains the commits of #3 too and adds
two new one. If it is the felix way, so may I provide a patch file instead of
git pull requests?
> DirectoryWatcher should not "refresh" Blueprint XML deployments on every
> start-up
> ---------------------------------------------------------------------------------
>
> Key: FELIX-4436
> URL: https://issues.apache.org/jira/browse/FELIX-4436
> Project: Felix
> Issue Type: Bug
> Components: File Install
> Affects Versions: fileinstall-3.2.4
> Environment: ServiceMix 4.5.3
> Reporter: metatech
> Priority: Minor
> Attachments: felix_no_refresh_installed.patch
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
