[
https://issues.apache.org/jira/browse/CAMEL-15310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17160624#comment-17160624
]
Christophe Willemsen commented on CAMEL-15310:
----------------------------------------------
Well, this is the whole purpose of this issue. I had two registered beans in
the same context and realised something was wrong when it was not picked up
correctly while passing the bean name as query parameter. So, actually the S3
component supports only 1 bean due to that hardcoded check of 1. When you have
two beans, none of the registry beans is actually used even when passing their
name in the endpoint.
A PullRequest with a test will make it clearer.
> AWS S3 - Support for more than 1 client in the registry
> -------------------------------------------------------
>
> Key: CAMEL-15310
> URL: https://issues.apache.org/jira/browse/CAMEL-15310
> Project: Camel
> Issue Type: Bug
> Components: camel-aws-s3
> Affects Versions: 3.1.0, 3.4.1
> Reporter: Christophe Willemsen
> Assignee: Andrea Cosentino
> Priority: Minor
>
> The `amazonS3Client` query parameter takes the key of the bean in the
> registry as argument, however that key is not used.
>
> Actually, today the component supports *ONLY* having 1 bean of type AmazonS3
> in the registry, the following method in the S3Component shows it :
>
>
> {code:java}
> private void checkAndSetRegistryClient(S3Configuration configuration) {
> Set<AmazonS3> clients =
> this.getCamelContext().getRegistry().findByType(AmazonS3.class);
> if (clients.size() == 1) {
>
> configuration.setAmazonS3Client((AmazonS3)clients.stream().findFirst().get());
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
