[
https://issues.apache.org/jira/browse/CAMEL-6108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13592471#comment-13592471
]
Raul Kripalani commented on CAMEL-6108:
---------------------------------------
Camel JMS is a true veteran and one of the most widely used components
alongside camel-cxf, camel-http and the ones embedded in camel-core. Given its
installation base, I don't think it's wise to refactor it into a whole
different technology base.
That said, I'd expect us (the Camel team) to encourage camel-sjms as the first
choice for JMS integration as soon as it's been more extensively tested in the
trenches, as Scott ES explains.
And perhaps do a few renames once that happens:
- camel-jms => camel-springjms
- camel-sjms => camel-jms
But it'd have to happen on a major release, so it's a very long-term vision.
> Refactor JMS Component to use JTA Transactions instead of Spring Transactions
> -----------------------------------------------------------------------------
>
> Key: CAMEL-6108
> URL: https://issues.apache.org/jira/browse/CAMEL-6108
> Project: Camel
> Issue Type: Improvement
> Components: camel-jms
> Reporter: Chris Geer
> Fix For: 3.0.0
>
>
> We love contributions as you know. May you find time to work on it?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
