GitHub user msparer opened a pull request:
https://github.com/apache/camel/pull/668
adapted the changes of CAMEL-8460 to only refresh routes on ContextReâ¦
â¦freshEvents from "own" applicationContext. Previously route refreshs
were initiated only if the parent applicationContext of the event's context was
null. This doesn't work when Spring instantiates the Camel's application
context as child of another applicationContext. This e.g. happens as soon as
you're using spring-cloud-config.
This proposed change brings back RouteCollector's constructor from camel
version 2.15.2 and aims to fix both [the initial reason for the
change](https://github.com/spring-cloud/spring-cloud-netflix/issues/438) and
the [bug introduced with the
change](https://issues.apache.org/jira/browse/CAMEL-8460).
Furthermore it should replace
[PR#666](https://github.com/apache/camel/pull/666)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/msparer/camel master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/668.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #668
----
commit 7d56055294e0bfe13acd336945e10249f37b3531
Author: msparer <[email protected]>
Date: 2015-11-03T11:01:14Z
adapted the changes of CAMEL-8460 to only refresh routes on
ContextRefreshEvents from "own" applicationContext. Previously route refreshs
were initiated only if the parent applicationContext of the event's context was
null. This doesn't work when Spring instantiates the Camel's application
context as child of another applicationContext. This e.g. happens as soon as
you're using spring-cloud-config
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
