[
https://issues.apache.org/jira/browse/CAMEL-14190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16979206#comment-16979206
]
Claus Ibsen edited comment on CAMEL-14190 at 11/21/19 11:55 AM:
----------------------------------------------------------------
Yeah the spring-boot docs is wrong, the nested configuration.xxx are duplicated
which they shouldn't.
So this is correct
camel.component.jms.connection-factory=#myConnectionFactory
And it works if I modify the spring-boot example on master
was (Author: davsclaus):
Yeah the spring-boot docs is wrong, the nested configuration.xxx are duplicated
which they shouldn't.
So this is correct
camel.component.jms.connection-factory=#myConnectionFactory
And it works if I modify the spring-boot example
> 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)
