> +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
Is the goal in binding error handlers here is to throw "more specific" type of
exceptions (as shown <a
href="https://github.com/jclouds/jclouds-labs/blob/master/cloudsigma2/src/main/java/org/jclouds/cloudsigma2/handlers/CloudSigmaErrorHandler.java#L46-L91";>here</a>
and <a
href="https://github.com/jclouds/jclouds-labs/blob/master/digitalocean/src/main/java/org/jclouds/digitalocean/handlers/DigitalOceanErrorHandler.java#L38-L58";>here</a>)
instead of a generic <code>org.jclouds.http.HttpResponseException?</code>
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/72/files#r17287382
