You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/12/06 14:37:59 UTC

[jira] [Commented] (CAMEL-10513) Start BlueprintCamelContext on BlueprintEvent.CREATED

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

ASF GitHub Bot commented on CAMEL-10513:
----------------------------------------

Github user hqstevenson closed the pull request at:

    https://github.com/apache/camel/pull/1297


> Start BlueprintCamelContext on BlueprintEvent.CREATED
> -----------------------------------------------------
>
>                 Key: CAMEL-10513
>                 URL: https://issues.apache.org/jira/browse/CAMEL-10513
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-blueprint
>            Reporter: Quinn Stevenson
>            Assignee: Quinn Stevenson
>            Priority: Minor
>             Fix For: 2.19.0
>
>
> Currently the BlueprintCamelContext starts when the BlueprintContainer OSGi service is registered.  Because of this, the startup of the BlueprintCamelContext can effect the startup of the BlueprintContainer itself, which can lead to infinite loops and make issues more difficult to resolve.
> The BlueprintCamelContext should be changed to start on the BlueprintEvent.CREATED, which is sent after the BlueprintContainer is fully initialized.



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