[
https://issues.apache.org/jira/browse/CAMEL-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang resolved CAMEL-5416.
---------------------------------
Resolution: Fixed
Fix Version/s: 2.11.0
I think we can resolve this issue, as the code has been committed into trunk
and we can create new issue if we have future enhancement on it.
> Camel Simple JMS Component
> --------------------------
>
> Key: CAMEL-5416
> URL: https://issues.apache.org/jira/browse/CAMEL-5416
> Project: Camel
> Issue Type: New Feature
> Reporter: Scott England-Sullivan
> Assignee: Willem Jiang
> Fix For: 2.11.0
>
> Attachments: CAMEL-5416.patch, camel-sjms.tar.gz,
> camel-sjms_wiki_documentation.txt
>
>
> I have developed a Camel JMS Component built with pure Java JMS APIs or
> Spring free. I would like to include it in the next 2.x release of Camel and
> am assuming that will be 2.11.
> Any guidance on how much lead time would be necessary to integrate it for
> that release would be appreciated (reads: when do you need the patch). :)
> _First Iteration:_
> * Full Queue and Topic Support (Durable & Non-Durable)
> * Full InOnly & InOut Support
> * Internal Connection, Session, Consumer, & Producer pooling/caching
> management
> * Full Asynchronous Support
> * JMS Internal Transaction Support
> _Future Iterations:_
> * Robust JMX Support
> * Camel Transaction Support
> * JTA Support (Pure Java)
> * Robust-InOnly
> * Full Migration of Core Camel-JMS Unit Tests (where applicable)
> * Batch List support
> Thanks,
> Scott ES
> http://fusesource.com
--
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
