[
https://issues.apache.org/jira/browse/SMX4-956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13969486#comment-13969486
]
metatech commented on SMX4-956:
-------------------------------
Is there any specific reason why the file "activemq-broker.xml" was not simply
moved from "etc" to "deploy", so that it is automatically redeployed ?
Adding a new DirectoryWatcher for this file implies that there are 2
DirectoryWatcher in total for this file : "etc/*" and
"etc/activemq-broker.xml". This double DirectoryWatcher is causing
interferences due to change done for FELIX-4436.
> Monitor etc/activemq-broker.xml for changes
> -------------------------------------------
>
> Key: SMX4-956
> URL: https://issues.apache.org/jira/browse/SMX4-956
> Project: ServiceMix 4
> Issue Type: Improvement
> Affects Versions: 4.3.0
> Reporter: Gert Vanthienen
> Assignee: Freeman Fang
> Fix For: 4.4.0
>
> Attachments: SMX4-956.patch
>
>
> When people want to change the configuration in {{etc/activemq-broker.xml}},
> they also have to explicitly do an {{osgi:update}} of the bundle or restart
> the container after removing the data directory. This is a bit inconvenient,
> but it also is confusing as all the other configuration files changes are
> being applied on the fly.
> We should configure FileInstall to also watch the {{etc/activemq-broker.xml}}
> for changes and automatically reconfigure stuff when necessary.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
