You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Antonin Stefanutti (JIRA)" <ji...@apache.org> on 2016/04/25 11:44:12 UTC

[jira] [Updated] (CAMEL-9904) Avoid creating an empty default Camel context in Camel CDI for empty deployments

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

Antonin Stefanutti updated CAMEL-9904:
--------------------------------------
    Fix Version/s: 2.17.1

> Avoid creating an empty default Camel context in Camel CDI for empty deployments
> --------------------------------------------------------------------------------
>
>                 Key: CAMEL-9904
>                 URL: https://issues.apache.org/jira/browse/CAMEL-9904
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-cdi
>            Reporter: Antonin Stefanutti
>            Assignee: Antonin Stefanutti
>            Priority: Minor
>             Fix For: 2.17.1, 2.18.0
>
>
> Camel CDI automatically deploys a Camel context to avoid user having to explicitly declare one.
> However, if the user mis-configures her/his application so that there is no route nor any other active components configured (like consumers), that leads to having an empty Camel context started.
> Besides, some runtimes automatically deploy the Camel CDI extension even in the case the user does not intent to use it, which leads to having an empty Camel context started.
> In both cases, the Camel CDI extension could rely on an heuristic (no routes, no consumers, ...) to avoid deploying that empty Camel context.



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