[
https://issues.apache.org/jira/browse/CAMEL-4400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14623643#comment-14623643
]
Mark Ford commented on CAMEL-4400:
----------------------------------
[~davsclaus] - See the original issue for the code for this feature:
CAMEL-3476. It's been 4 years since the code was contributed. There is some
discussion in the JIRA comments about why the code was never merged but as I
recall, a lot of the discussion took place among the committers offline. These
discussions are referenced in the committer's comments but no substance is
provided.
There have since been a couple of requests for this feature since then but I
don't think it's worth pursuing unless there's a committer willing to merge the
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)
