You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2015/07/11 23:47:05 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=14623585#comment-14623585 ] 

Claus Ibsen commented on CAMEL-4400:
------------------------------------

[~massfords] are you willing to contribute your work? Sorry for not getting back sooner, but walking through old tickets now.
You could potentially just .zip all the source from that project and attach to this JIRA - then we have permission to use your work.

> Consumer Endpoint for AWS SNS Service
> -------------------------------------
>
>                 Key: CAMEL-4400
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4400
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-aws
>            Reporter: Kai Wähner
>             Fix For: Future
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)