[
https://issues.apache.org/jira/browse/CAMEL-6715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-6715.
--------------------------------
Resolution: Fixed
Assignee: Claus Ibsen
Fix Version/s: (was: Future)
3.0.0.M5
3.0.0
Updated the docs
> 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, osgi
> Affects Versions: 2.11.2, 2.12.0
> Reporter: Ievgen Tarasov
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 3.0.0, 3.0.0.M5
>
> 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
(v7.6.14#76016)
