[
https://issues.apache.org/jira/browse/CAMEL-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13010309#comment-13010309
]
Mark Ford commented on CAMEL-3476:
----------------------------------
I don't understand why the producer would create the subscription. Why would
you tightly couple the production of messages with the consumption of messages?
The duplication of code is irrelevant. Tracy can refactor this so the SNS
consumer is nothing more than an instantiation of the SQS consumer.
Multiple subscribers already work with the SNS component as it is. Each route
would create the from with the same topic name or ARN and then use their own
SQS endpoint (by name or ARN) to receive the messages.
I think I've already encapsulated the details of the subscription pretty well
in the component. When I am creating a route to read messages from an endpoint,
I am only focused on the messages I'm receiving and not how I am receiving
them. These details are encapsulated in the component with the creation of a
temporary queue. With your model, you must configure the subscription
externally.
> 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.8.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
