You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2021/09/23 08:08:00 UTC

[jira] [Resolved] (CAMEL-16995) [camel-karaf] Support multiple CamelContexts in CamelBlueprintTestSupport

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

Claus Ibsen resolved CAMEL-16995.
---------------------------------
    Resolution: Fixed

> [camel-karaf] Support multiple CamelContexts in CamelBlueprintTestSupport
> -------------------------------------------------------------------------
>
>                 Key: CAMEL-16995
>                 URL: https://issues.apache.org/jira/browse/CAMEL-16995
>             Project: Camel
>          Issue Type: Improvement
>          Components: karaf
>    Affects Versions: 3.11.2
>            Reporter: Gert Vanthienen
>            Assignee: Gert Vanthienen
>            Priority: Major
>             Fix For: 3.12.0
>
>
> When using the CamelBlueprintTestSupport class on a larger project, you can easily end up with a situation where multiple bundles contain Blueprint descriptors containing a CamelContext.
> The CamelBlueprintTestSupport class currently uses the first available CamelContext in the registry, but it would be nice if you could explicitly indicate which context you want to test. An OSGi filter expression would be a good way to do that.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)