You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Daniel Carleton (Commented) (JIRA)" <ji...@apache.org> on 2012/03/23 18:09:27 UTC

[jira] [Commented] (CAMEL-4400) Consumer Endpoint for AWS SNS Service

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

Daniel Carleton commented on CAMEL-4400:
----------------------------------------

So the approach would be to automatically create an SQS queue, subscribe it to the SNS topic, and then consume that?
                
> Consumer Endpoint for AWS SNS Service
> -------------------------------------
>
>                 Key: CAMEL-4400
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4400
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-aws
>            Reporter: Kai Wähner
>             Fix For: 2.10.0
>
>
> Contrary to S3 and SQS, Camel only offers a producer endpoint for this AWS service. You can only create topics and send messages via Camel. The reason is simple: Camel already offers endpoints for consuming these messages: HTTP, Email and SQS are already available.
> But there is a huge tradeoff: A consumer cannot subscribe to topics using Camel. The AWS Management Console has to be used.
> The original contribution of camel-sns contained a consumer for easily configuring and consuming the data from the topic. This was not included in the release.
> The SNS consumer should be added, because otherwise Camel is missing a core feature of the AWS SNS service.

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