> + case 402:
> + exception = new IllegalStateException(message, exception);
> + break;
> + case 404:
> + if
> (!command.getCurrentRequest().getMethod().equals("DELETE")) {
> + exception = new ResourceNotFoundException(message,
> exception);
> + }
> + break;
> + case 405:
> + exception = new IllegalArgumentException(message, exception);
> + break;
> + case 409:
> + exception = new IllegalStateException(message, exception);
> + break;
> + case 500:
> + exception = null;
This issue now appears to be a red-herring IMO. With the response now coming
back as "null" upon resource not being found jclouds successfully returns this
as a null object instead of throwing an error trying to convert it to json. I
think we are safe moving forward with no needed Fallback implementation or
returning of null on 500. I think this is as happy a path as we can expect.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/116/files#r22237334
