You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Martin Lichtin (JIRA)" <ji...@apache.org> on 2015/09/01 21:36:48 UTC

[jira] [Commented] (CAMEL-8770) Camel Blueprint - depends-on does not work

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

Martin Lichtin commented on CAMEL-8770:
---------------------------------------

Hi Willem thanks for the fix. Something definitely changed with 2.15.3 :)
I've so far been referring to several beans with depends-on="beanA,beanB"
However, this (obviously) no longer works. It seems depends-on does not support a list (unlike the depends-on in Aries Blueprint).
How then can one make the CamelContext depend on more than one bean?

> Camel Blueprint - depends-on does not work
> ------------------------------------------
>
>                 Key: CAMEL-8770
>                 URL: https://issues.apache.org/jira/browse/CAMEL-8770
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-blueprint
>    Affects Versions: 2.14.2, 2.15.2
>            Reporter: Willem Jiang
>            Assignee: Willem Jiang
>             Fix For: 2.14.3, 2.15.3, 2.16.0
>
>
> Attribute depends-on does not work for camelContext element in blueprint container. When bean XXX does not exist then an exception should be thrown like in spring container.
> {code}
> <camelContext ... depends-on="XXX">
> {code}



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