> +com.google.inject.ConfigurationException: Guice configuration errors:
> +
> +1) No implementation for org.jclouds.rackspace.cloudfiles.v1.CloudFilesApi
> was bound.
> + while locating org.jclouds.rackspace.cloudfiles.v1.CloudFilesApi
> + ...
> +```
> +
> +This is caused by a misconfiguration when creating a view or api.
> +
> +{% highlight java %}
> +CloudFilesApi cloudFilesApi = ContextBuilder.newBuilder("openstack-swift")
> + .credentials(username, apiKey)
> + .buildApi(CloudFilesApi.class);
> +{% endhighlight %}
> +
> +The provider String you pass to `ContextBuilder.newBuilder(String)` must
> match the view or api you are creating.
The first comment calls the code below a "misconfiguration" and the next
comment tells the user what they must do with the code below that. I don't see
an ambiguity here.
Pointing users at the API or provider metadata classes would be sending them
all over the place and causing greater confusion. The metadata classes are an
implementation detail that should be hidden from users.
I think this points to a hole in our current docs. We have no *single* page
that lists all APIs/Providers.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/94/files#r12261644
