Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Thu, 2 Aug 2012 08:21:02 +0000 (UTC)
From: "Willem Jiang (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <245828753.4338.1343895662802.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <1785645011.148.1341346955375.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Assigned] (CAMEL-5416) Camel Simple JMS Component
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CAMEL-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Willem Jiang reassigned CAMEL-5416:
-----------------------------------

    Assignee: Willem Jiang
    
> 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
>         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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira