[
https://issues.apache.org/jira/browse/CAMEL-6715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13768997#comment-13768997
]
Eugene Tarasov commented on CAMEL-6715:
---------------------------------------
Yes, that would be great. Also, I think it would be helpful to update
documentation with this info. I mean these pages:
http://camel.apache.org/blueprint-testing.html
http://camel.apache.org/spring-testing.html
For blueprint-testing.html something like this could be added after words "you
can specify them with a comma-separated list in the getBlueprintDescriptor
method.":
bq. However, only *one* of them can have a Camel Context (i.e. there can be
only one Camel Context per test bundle).
For spring-testing.html I dont see so obvious please where it can be added.
Maybe a _note_ at the end of "CamelSpringTestSupport" section. Something like:
bq. Only one Camel Context per test is supported.
> 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: Eugene Tarasov
> Priority: Minor
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
