camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Müller (JIRA) <>
Subject [jira] Commented: (CAMEL-3468) New camel-aws component
Date Fri, 31 Dec 2010 13:01:51 GMT


Christian Müller commented on CAMEL-3468:

@Claus: I think we should postpone it to 2.7, because we also need the OSGI-fied version of
the aws-java-sdk.

@Tracy: The resultExchange in the last line was a typo.
The SqsBinding only holds the SQS constants. Maybe we find a better name for it...
public class SqsBinding {

    public static final String MD5_OF_BODY = "CamelSqsMD5OfBody";
    public static final String MESSAGE_ID = "CamelSqsMessageId";
    public static final String RECEIPT_HANDLE = "CamelSqsReceiptHandle";
The integration test is now working fine. I would like to add/change the following thinks:
- deleting of consumed messages after the successful processing in Camel
- provide the option to configure a client in the URL like "sqs://MyQueue?accessKey=xxx&secretKey=yyy&client=#myAmazonSQSClient"
to have the possibility to share and mock the client
- provide the option to configure a header filter strategy. All not filtered header will be
send as message attributes to SQS
- add some log statements
- add some "real" Camel tests which use an AmazonSQSClient mock

> New camel-aws component
> -----------------------
>                 Key: CAMEL-3468
>                 URL:
>             Project: Camel
>          Issue Type: New Feature
>            Reporter: Tracy Snell
>            Assignee: Christian Müller
>             Fix For: 2.6.0
>         Attachments: patchfile.txt
> I've started a new component to interface with Amazon Web Services. This first pass includes
just a Simple Queue Service component. Additional services will be added soon. I used the
Amazon AWS SDK for Java to interface with AWS. Uses Apache 2.0 as it's license.
> Let me know if I need to change things or any thoughts/suggestions and I'll be glad to
make the adjustments.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message