[
https://issues.apache.org/jira/browse/CAMEL-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13001205#comment-13001205
]
Mark Ford commented on CAMEL-3476:
----------------------------------
I think there's value in having a way to stand up a subscription to a topic
from camel. Imagine if the AMQP or JMS components didn't offer this ability. I
know it's slightly different because of how those protocols are implemented but
I think this is part of the value of camel's endpoint abstraction. The value
add from the use of the component is that it encapsulates the additional
administrative details. Changing from Amazon SNS to AMQP should be a simple
matter of changing the endpoint URI's in your config and then changing the
dependencies. Requiring an additional administrative step to go the Amazon
admin console doesn't sound right.
I don't know how many people would use it this way versus administering it
outside of camel but it's nice to have the option.
> Contribute camel-sns component to the new camel-aws component.
> --------------------------------------------------------------
>
> Key: CAMEL-3476
> URL: https://issues.apache.org/jira/browse/CAMEL-3476
> Project: Camel
> Issue Type: New Feature
> Components: camel-aws
> Affects Versions: 2.6.0
> Reporter: Mark Ford
> Assignee: Christian Müller
> Priority: Minor
> Fix For: 2.7.0
>
> Attachments: camel-aws-3476.txt, patchfile.txt, patchfile.txt
>
>
> CAMEL-3468 contributes a new component for interacting with the Amazon SQS
> service. The camel-sns component allows users to publish/subscribe to topics
> on Amazon's Simple Notification Service.
> This code is currently hosted as a google code project here:
> http://code.google.com/p/camel-sns/
> I'll coordinate with Tracy (developer of camel-aws) in the creation of the
> patch.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
