You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Edward Ost (JIRA)" <ji...@apache.org> on 2014/11/07 16:53:34 UTC

[jira] [Commented] (CAMEL-7898) Support Multiple Context with CamelBlueprintTestSupport

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

Edward Ost commented on CAMEL-7898:
-----------------------------------

I have windows EC2 instance that I would be happy to provide access to for anyone who wants to work on the issue.

> Support Multiple Context with CamelBlueprintTestSupport 
> --------------------------------------------------------
>
>                 Key: CAMEL-7898
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7898
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-blueprint
>    Affects Versions: 2.13.2
>            Reporter: Edward Ost
>            Priority: Minor
>
> CamelBlueprintTestSupport is great, but it only supports one context.  This limits it usefulness in an enterprise SOA environment where test fixtures are themselves implemented as test routes.  This is documented correctly at http://camel.apache.org/blueprint-testing.html .  But because of this bug you cannot use blueprint since the camel contexts for the new routes are not picked up.  For test fixtures this could possibly be worked around by perhaps adding the test routes directly with Camel Context components.  But even then we cannot compose multiple production camel contexts for extended integration testing.  Fixing this one small limitation would remove a lot of obstacles and complexity and promote more use of blueprint with Camel in an enterprise context.



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