camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott England-Sullivan (JIRA)" <>
Subject [jira] [Commented] (CAMEL-5416) Camel Simple JMS Component
Date Tue, 07 Aug 2012 01:01:19 GMT


Scott England-Sullivan commented on CAMEL-5416:

Hi Babak,

It does exist, just not in trunk yet. :S

I submitted it as part of the CAMEL-5486 subtask.  The patch has some issues so Willem is
going to go through it with me tonight.

For the time being you would only need that for a durable subscription so for the sake of
the examples today it isn't needed.  It contains some refactoring that brings it into alignment
with the JMS spec though.  Hopefully we will be through it tonight.  If not I will pull it
out of the docs until we can get it in. 

I will send out an update when we are done.

Scott ES
> Camel Simple JMS Component
> --------------------------
>                 Key: CAMEL-5416
>                 URL:
>             Project: Camel
>          Issue Type: New Feature
>            Reporter: Scott England-Sullivan
>            Assignee: Willem Jiang
>         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
> 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

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message