[jira] [Resolved] (CAMEL-16029) camel-core - Log on startup if multiple instances of same component are in use

["Claus Ibsen (Jira)" <ji...@apache.org>]

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

Claus Ibsen resolved CAMEL-16029.
---------------------------------
    Resolution: Fixed

> camel-core - Log on startup if multiple instances of same component are in use
> ------------------------------------------------------------------------------
>
>                 Key: CAMEL-16029
>                 URL: https://issues.apache.org/jira/browse/CAMEL-16029
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-core
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Major
>             Fix For: 3.8.0
>
>
> Mostly you would use the default component instances. But for messaging components like JMS you may have one for ActiveMQ and another for WMQ etc and therefore multiple instances in the same Camel.
> However with SB you can mistakenly configure a new JMS component such as
> @Bean
> JmsComponent jmsComponent() {
>  ...
> }
> And think that "jms" will use it. But it uses the bean id, which is method name by default in SB, so you have 2 JMS components.
> Having a LOG at startup to help show this would better spot this problem.



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