[ 
https://issues.apache.org/jira/browse/CAMEL-9161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14998668#comment-14998668
 ] 

ASF GitHub Bot commented on CAMEL-9161:
---------------------------------------

GitHub user nstuart opened a pull request:

    https://github.com/apache/camel/pull/674

    CAMEL-9161 Change for dealing with parent contexts

    Changes to look at current status instead of just checking for parent 
context. Using spring cloud automatically adds a parent context which 
completely disables camel-spring-boot stuff from 2.15.3 onwards.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/nstuart/camel master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/camel/pull/674.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 #674
    
----
commit 4257aaba6dece76f0649bb5c263bbb6b6558e5cd
Author: Nick Stuart <n...@portlandwebworks.com>
Date:   2015-11-10T14:19:07Z

    CAMEL-9161 Change for dealing with parent contexts

----


> Camel spring-boot not finding routes.
> -------------------------------------
>
>                 Key: CAMEL-9161
>                 URL: https://issues.apache.org/jira/browse/CAMEL-9161
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-spring-boot
>    Affects Versions: 2.15.3, 2.16.0
>            Reporter: Nicholas Stuart
>            Assignee: Henryk Konsek
>         Attachments: camel-boot-test.tar.gz
>
>
> On startup Camel is not registering any routes annotated with @Component. 
> Route is found and registered in Spring just fine. Switch to version 2.15.2 
> and it works fine. 
> No errors are thrown, and everything says it's started, but no routes are 
> active or reported as being found during startup. 
> Application is being run through `mvn spring-boot:run` if that makes a 
> difference.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to