camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-6850) Allow AWS SQS to not ack or even if it doesn't encounter an exception
Date Fri, 11 Oct 2013 10:32:42 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-6850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13792510#comment-13792510
] 

Claus Ibsen commented on CAMEL-6850:
------------------------------------

Ah didnt spot it was in an unit test. But still nice to cleanup nicely.

I am applying the patch. Can you do the documentation update?

> Allow AWS SQS to not ack or even if it doesn't encounter an exception
> ---------------------------------------------------------------------
>
>                 Key: CAMEL-6850
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6850
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-aws
>    Affects Versions: 2.12.1
>            Reporter: Christian Posta
>            Assignee: Christian Posta
>             Fix For: 2.12.2, 2.13.0
>
>         Attachments: CAMEL-6850-update1.patch
>
>
> Since SQS doesn't allow selectors it could be nice to use camel's filtering and ignore
messages that don't fit through that filter. Right now DeleteMessage is sent back onCompletion.
Proposed is to set a header of some other facility to let the onCompletion know that even
though there wasn't a failure, still don't send back the ack/delete message. I'll work on
a patch.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message