Thanks for reporting! I created a ticket [1] and fixed this for all supported AmazonXXX Interfaces. Please close the pull request.
[1] https://issues.apache.org/jira/browse/CAMEL-6177 Best, Christian On Tue, Mar 12, 2013 at 4:39 PM, saurabhksingh <g...@git.apache.org> wrote: > GitHub user saurabhksingh opened a pull request: > > https://github.com/apache/camel/pull/15 > > making change so that we can use camel-aws integration to make use of > ot... > > ...her implementations of AmazonSQS instead of tightly binding it to > AmazonSQSClient. > > making change so that we can use camel-aws integration to make use of > other implementations of AmazonSQS instead of tightly binding it to > AmazonSQSClient. For example this also allows us to make use of > AmazonSQSBufferedAsyncClient if we want to. > > You can merge this pull request into a Git repository by running: > > $ git pull https://github.com/saurabhksingh/camel trunk > > Alternatively you can review and apply these changes as the patch at: > > https://github.com/apache/camel/pull/15.patch > > ---- > commit 9030299add2a60e2938dbd8dafbf8e589ebef519 > Author: Saurabh Kr Singh <saurabh.n...@gmail.com> > Date: 2013-03-12T15:01:07Z > > making change so that we can use camel-aws integration to make use of > other implementations of AmazonSQS instead of tightly binding it to > AmazonSQSClient. > > making change so that we can use camel-aws integration to make use of > other implementations of AmazonSQS instead of tightly binding it to > AmazonSQSClient. For example this also allows us to make use of > AmazonSQSBufferedAsyncClient if we want to. > > ---- > > --
