Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Tue, 16 Apr 2013 11:35:15 +0000 (UTC)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12642687.1366104395553.173115.1366112115883@arcas>
In-Reply-To: <JIRA.12642687.1366104395553@arcas>
References: <JIRA.12642687.1366104395553@arcas>
Subject: [jira] [Resolved] (CAMEL-6286) Make SqsConsumer support async
 processors
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Claus Ibsen resolved CAMEL-6286.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 2.11.0
         Assignee: Claus Ibsen

Thanks for the patch. I med the S3 consumer support async as well.
                
> Make SqsConsumer support async processors
> -----------------------------------------
>
>                 Key: CAMEL-6286
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6286
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-aws
>    Affects Versions: 2.10.4
>         Environment: N/A
>            Reporter: alex hutter
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.11.0
>
>         Attachments: aws-async.patch
>
>
> Switch SqsConsumer from using getProcessor().process() to getAsyncProcessor().process() with a callback to allow use of async processors.
> As I understand it is ok to always use the async processor call as its to show that 'the caller supports having the exchange asynchronously processed' rather than specifically always process it asynchronously.

--
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