[ 
https://issues.apache.org/jira/browse/JCLOUDS-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15827725#comment-15827725
 ] 

ASF subversion and git services commented on JCLOUDS-1227:
----------------------------------------------------------

Commit 36cb2a1c72076b4e7200599911ab18c1078867bd in jclouds's branch 
refs/heads/master from [~nacx]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=36cb2a1 ]

JCLOUDS-1227: Allow to configure regions with the same URI


> Unable to configure property based regions if all have the same URL
> -------------------------------------------------------------------
>
>                 Key: JCLOUDS-1227
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-1227
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-core
>    Affects Versions: 2.0.0
>            Reporter: Ignasi Barrera
>            Assignee: Ignasi Barrera
>
> When configuring the regions of a provider using the context properties, if 
> there are no specific endpoints for each region, the following exception is 
> thrown:
> {code}
> Multiple entries with same value: <regionId1>=<endpoint> and 
> <regionId2>=<endpoint>
> java.lang.IllegalArgumentException
>       at 
> com.google.common.collect.ImmutableMap.checkNoConflict(ImmutableMap.java:150)
>       at 
> com.google.common.collect.RegularImmutableBiMap.<init>(RegularImmutableBiMap.java:131)
>       at 
> com.google.common.collect.ImmutableBiMap.copyOf(ImmutableBiMap.java:210)
>       at 
> org.jclouds.suppliers.SupplyKeyMatchingValueOrNull.get(SupplyKeyMatchingValueOrNull.java:53)
> {code}
> This is caused by the use of a Guava BiMap in the 
> [SupplyKeyMatchingValueOrNull|https://github.com/jclouds/jclouds/blob/master/core/src/main/java/org/jclouds/suppliers/SupplyKeyMatchingValueOrNull.java],
>  which enforces unique keys and values.
> The implementation should be changed to allow regions being configured in the 
> context properties.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to