> +import org.jclouds.rest.ConfiguresHttpApi;
> +import org.jclouds.rest.config.HttpApiModule;
> +
> +/**
> + * Configures the {@link org.jclouds.profitbricks.ProfitBricksApi}
> connection.
> + */
> +@ConfiguresHttpApi
> +public class PBHttpApiModule extends HttpApiModule<ProfitBricksApi> {
> +
> + @Override
> + protected void bindErrorHandlers() {
> + }
> +
> + @Override
> + protected void bindRetryHandlers() {
> + // TODO configure handling of client and server error
Yes. We try to propagate more specific (and semantically more appropriate)
exceptions so dealing with the different failures is easy in the client code.
The exceptions that jclouds can propagate from the error handlers can be found
[here](https://github.com/jclouds/jclouds/blob/master/core/src/main/java/org/jclouds/util/Throwables2.java#L128-L138).
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/72/files#r17288231
