[
https://issues.apache.org/jira/browse/CAMEL-14190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16979109#comment-16979109
]
Claus Ibsen commented on CAMEL-14190:
-------------------------------------
The example camel-example-spring-boot-activemq is using spring boot activemq
starter and not Camel's starter. So its SB that setup ActiveMQ broker, and
Camel just uses it, where it in JmsComponent does the auto-lookup of the CF.
(so the camel-jms-starter is not in use at all)
> JMSComponent tries to use applicationContext before it is initialised
> ---------------------------------------------------------------------
>
> Key: CAMEL-14190
> URL: https://issues.apache.org/jira/browse/CAMEL-14190
> Project: Camel
> Issue Type: Bug
> Components: camel-jms
> Affects Versions: 3.0.0.RC3
> Reporter: Constantino Cronemberger
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 3.0.0
>
>
> The method getConfiguration checks if applicationContext is null. If not it
> will try to automatically initialise the ConnectionFactory and the
> DestinationResolver.
> The problem is that applicationContext will always be null when used with
> JmsComponentAutoConfiguration (or the corresponding classes in other similar
> starters) because the method setApplicationContext is called only after the
> method that creates the bean returns and because the auto configuration class
> also calls CamelPropertiesHelper.setCamelProperties which in turn calls
> getConfiguration.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
