[
https://issues.apache.org/jira/browse/CAMEL-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13640308#comment-13640308
]
Willem Jiang commented on CAMEL-6305:
-------------------------------------
It's hard to block the starting process of BlueprintCamelContext before the
bundle is start, because CamelContext will be publish as OSGi service after the
BlueprintCamelContext is started. And CamelBlueprintTestSupport is looking up
the CamelContext from the OSGi service registry.
I finally find a way to fix this issue by just stop the CamelContext in the
setUp method if we need the debug feature.
> debugBefore() and debugAfter() not called if unit test extends
> CamelBlueprintTestSupport
> ----------------------------------------------------------------------------------------
>
> Key: CAMEL-6305
> URL: https://issues.apache.org/jira/browse/CAMEL-6305
> Project: Camel
> Issue Type: Bug
> Components: camel-core, camel-test
> Affects Versions: 2.11.0
> Reporter: Torsten Mielke
> Assignee: Willem Jiang
> Attachments: CAMEL-6305.diff
>
>
> A test that extends CamelBlueprintTestSupport does not get its debugBefore()
> and debugAfter() methods called.
--
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
