If there is a specific API call in SoftLayer that sometimes throws that unexpected error, shouldn't it be more appropriate to create a custom ExceptionParser for that API call, and let it transform the api response into the appropriate return value, rather than adding this try/catch everywhere you might get this error?
--- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/199#issuecomment-28217619
