[
https://issues.apache.org/jira/browse/CAMEL-10513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15687915#comment-15687915
]
ASF GitHub Bot commented on CAMEL-10513:
----------------------------------------
GitHub user hqstevenson opened a pull request:
https://github.com/apache/camel/pull/1297
CAMEL-10513: Start BlueprintCamelContext on BlueprintEvent.CREATED
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hqstevenson/camel CAMEL-10513
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/1297.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1297
----
commit 1deed29da73fcdf77ba144cc03d6e8af7a06043e
Author: Quinn Stevenson <[email protected]>
Date: 2016-11-22T21:15:53Z
CAMEL-10513: Start BlueprintCamelContext on BlueprintEvent.CREATED
----
> 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: Grzegorz Grzybek
> Priority: Minor
>
> 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)
