[
https://issues.apache.org/jira/browse/CAMEL-9916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15262068#comment-15262068
]
Catalina-Alina Dobrica commented on CAMEL-9916:
-----------------------------------------------
This fix is needed but it doesn't fix the bigger part of this ticket: it does
not add the feature of nodev/XML sjms (so that the SjmsComponent instance is
not needed beforehand and required to be activated outside the route with a
ConnectionFactory). Also, I need the connection factory on the endpoint level
because in a setup of multiple camel contexts sharing the same registry I am
restricted to using a single server or creating a new instance of sjms
component with a different name for each server, and {code}sjms connection
setup with options + sjms:queue:test, sjms2 setup with options +
sjms2:queue:test, ... {code} is not nodev friendly, while
{code}sjms:queue:test[?options]{code} with the connection configuration behind
the scenes is much easier to use.
Also, the idea is not that I want to share a pool across multiple camel
contexts, it is that I don't want to, but _I am forced to share it_ when I am
restricted to using the same registry for multiple contexts.
> 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)
