[jira] [Updated] (CAMEL-6715) camel-test-blueprint - Only one Camel context gets started on test startup

["Claus Ibsen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CAMEL-6715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated CAMEL-6715:
-------------------------------
    Fix Version/s:     (was: 2.16.0)
                   2.17.0

> camel-test-blueprint - Only one Camel context gets started on test startup
> --------------------------------------------------------------------------
>
>                 Key: CAMEL-6715
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6715
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-test
>    Affects Versions: 2.11.2, 2.12.0
>            Reporter: Ievgen Tarasov
>             Fix For: 2.17.0
>
>         Attachments: JUnit_MultipleContexts.patch
>
>
> In a test made with camel-test-blueprint, and where there is more than one Camel context per Bundle, only one of them gets started. Actually this problem was introduced with the fix for CAMEL-6524. Before the fix every Camel Context would be started after it was created. Now only a context which is "associated" with the test is getting started.
> For camel-test-spring there is a similar problem. Though it looks to me that in spring multiple contexts didnt work even before CAMEL-6524.
> I've attached a patch that introduces a simple junit test for this problem (for both blueprint and spring).



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