Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Fri, 22 Apr 2016 14:19:12 +0000 (UTC)
From: "Antonin Stefanutti (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12961653.1461334738000.8789.1461334752905@Atlassian.JIRA>
In-Reply-To: <JIRA.12961653.1461334738000@Atlassian.JIRA>
References: <JIRA.12961653.1461334738000@Atlassian.JIRA>
 <JIRA.12961653.1461334738312@arcas>
Subject: [jira] [Created] (CAMEL-9904) Avoid creating an empty default Camel
 context in Camel CDI for empty deployments
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Antonin Stefanutti created CAMEL-9904:
-----------------------------------------

             Summary: 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.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)