[
https://issues.apache.org/jira/browse/LIBCLOUD-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114027#comment-13114027
]
Tomaz Muraus edited comment on LIBCLOUD-114 at 9/24/11 5:58 PM:
----------------------------------------------------------------
Can you provide a concreate example please?
You should be able to handle cases like this in a custom Response class.
was (Author: kami):
Can you provide a concreate example please?
You should be able to handle cases like this in a custom _Response_ class.
> Provider HTTP Error responses need to be propagated in a better way.
> --------------------------------------------------------------------
>
> Key: LIBCLOUD-114
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-114
> Project: Libcloud
> Issue Type: Improvement
> Components: Core
> Reporter: Brian Hoenig
> Priority: Minor
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Currently when a provider returns an unexpected (error) response the response
> code and message must be parsed from a message string in a base Exception.
> Instead we should include the error code and error message in an exception
> class (ProviderHTTPResponseError).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
