You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Antoine DESSAIGNE (JIRA)" <ji...@apache.org> on 2016/05/11 08:35:13 UTC

[jira] [Commented] (CAMEL-9916) SJMS component is not currently nodev/XML route compatible

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

Antoine DESSAIGNE commented on CAMEL-9916:
------------------------------------------

Hi Claus,

Right now, in the {{sjms}} component, the connection factory is configured in the component and not in the endpoint. It has several drawbacks :
* You cannot simply use {{from("sjms:...")}} in a route, you need to configure the component for the connection
* You cannot have 2 {{sjms}} endpoint in a single context, you need to declare it with another name
With this pull-request, you can still configure the connection at the component level but also at the endpoint

Also, there was a mechanism that automatically creates a connection pool (named {{ConnectionFactoryResource}}). In order to be consistent, this pull-request now automatically closes the pool on shutdown in order to properly release resources.

Antoine


> SJMS component is not currently nodev/XML route compatible
> ----------------------------------------------------------
>
>                 Key: CAMEL-9916
>                 URL: https://issues.apache.org/jira/browse/CAMEL-9916
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-sjms
>            Reporter: Catalina-Alina Dobrica
>
> SJMS component is currently not friendly for XML route usage because:
> * You need a component instance which has been "activated" - has had a connection factory set.
> * On route restart, the component cannot be reused because the underlying pool is closed and not recreated



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)