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

ASF GitHub Bot commented on CAMEL-9916:
---------------------------------------

GitHub user near-ethic opened a pull request:

    https://github.com/apache/camel/pull/965

    CAMEL-9916 Allow configuration of connectionFactory& co in SjmsEndpoint

    Allow sjms endpoints to be used without requiring prior initialization of 
the component with a connection factory to make this endpoint xml friendly. The 
new endpoint usage is also friendly to context restart

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/near-ethic/camel CAMEL-9916

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/camel/pull/965.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #965
    
----
commit 64cff850a6ad50e806a68601ecbd6c811ce53554
Author: near-ethic <dark.cather...@gmail.com>
Date:   2016-04-25T10:25:12Z

    Allow sjms endpoints to be used without requiring prior initialization of 
the component with a connection factory to make this endpoint xml friendly. The 
new endpoint usage is also friendly to context restart

----


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

Reply via email to