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/02/01 13:55:00 UTC

[jira] [Updated] (CAMEL-15555) RouteTemplates creating in CDI are configured out-of-order

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

Claus Ibsen updated CAMEL-15555:
--------------------------------
    Fix Version/s:     (was: 3.8.0)
                   3.9.0

> RouteTemplates creating in CDI are configured out-of-order
> ----------------------------------------------------------
>
>                 Key: CAMEL-15555
>                 URL: https://issues.apache.org/jira/browse/CAMEL-15555
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-cdi
>    Affects Versions: 3.5.0
>            Reporter: Paul Campbell
>            Priority: Minor
>             Fix For: 3.9.0
>
>
> When:
>  * using Camel with CDI
>  * having routes defined in multiple beansĀ 
>  * one bean defines the route template
>  * another bean attempts to create a route from that template
> I would expect that the route templates are configured before any routes that build from them.
> What happens is non-deterministic based on the order the RoutesBuilder instances are provided by the CDI runtime. In a good case, the template bean is processed first and all is as-expected. However, when the template bean is provided after any bean that attempts to build from it we get the error:
> {{Caused by: java.lang.IllegalArgumentException: Cannot find RouteTemplate with id ListProcess}}
> {{ at org.apache.camel.quarkus.core.BaseModel.addRouteFromTemplate(BaseModel.java:167)}}
> {{ at org.apache.camel.quarkus.core.FastCamelContext.addRouteFromTemplate(FastCamelContext.java:188)}}
> {{ at org.apache.camel.builder.TemplatedRouteBuilder.add(TemplatedRouteBuilder.java:104)}}
> Attempted a workaround by annotating the template bean with @Priority(1), however this had no effect.



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