You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2019/11/19 08:25:00 UTC

[jira] [Commented] (CAMEL-14190) JMSComponent tries to use applicationContext before it is initialised

    [ https://issues.apache.org/jira/browse/CAMEL-14190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16977237#comment-16977237 ] 

Claus Ibsen commented on CAMEL-14190:
-------------------------------------

Can you tell more about in which use-case you have this problem - the camel-jms component are very much in use and we havent got any issues reported before like this.

> 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)