[ https://issues.apache.org/jira/browse/CAMEL-9916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15261969#comment-15261969 ]
Catalina-Alina Dobrica commented on CAMEL-9916: ----------------------------------------------- Although this would solve a single-context use-case, it's not the full solution for me. My original use-case is one where multiple contexts share the same registry which won't be fixed by keeping custom added components because when one of the contexts stops, the pool on the component is closed and the other contexts can no longer get a connection (java.lang.IllegalStateException: Pool not open) > 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)