[
https://issues.apache.org/jira/browse/CAMEL-14190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16977819#comment-16977819
]
Constantino Cronemberger edited comment on CAMEL-14190 at 11/19/19 8:24 PM:
----------------------------------------------------------------------------
I have debugged some tests in the camel-jms module and found that the order of
the calls to JmsComponent.getConfiguration and
JmsComponent.setApplicationContext is actually the opposite of what happens
when running with Spring Boot.
Looks like the major challenge to fix this issue will be to rework the tests
and not the actual fix.
Or maybe the code should be prepared to work no matter the order of the calls
to those methods.
was (Author: ccronemberger):
I have debugged some tests in the camel-jms module and found that the order of
the calls to JmsComponent.getConfiguration and
JmsComponent.setApplicationContext is actually the opposite of what happens
when running with Spring Boot.
Looks like the major challenge to fix this issue will be to rework the tests
and not the actual fix.
> 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
> Priority: Minor
>
> 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)
