Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Exception hierarchy

See original GitHub issue

Python has defined an exception hierarchy in the following form:

AzureError
  |- AzureLibraryError
      |- AzureLibraryRequestError
      |- AzureLibraryResponseError
  |- ServiceRequestError
      |- ConnectionTimeoutError
      |- ServiceHttpRequestError
          |- ClientRequestError
              |- ResourceExistsError
              |- ClientAuthenticationError
              |- ResourceModifiedError
          |- ServerError
          |- TooManyRedirectsError
          |- TooManyRetriesError

We need to develop a similar exception hierarchy that is idiomatic for Java developers.

Issue Analytics

State:
Created 4 years ago
Comments:18 (18 by maintainers)

Top GitHub Comments

1reaction

JonathanGilescommented, Mar 31, 2019

Todo:

Create a new package in azure-common com.azure.common.exception
We should repurpose the existing RestException class into ServiceRequestException, and relocate it into this package.
We build out the additional exception types and ensure that they are tested,
Ensure that Reactor properly propagates unchecked exceptions from the http pipeline through to the end user.

0reactions

JonathanGilescommented, May 1, 2019

@sima-zhu @alzimmermsft I still don’t understand what is being said here. Can you point to exactly what you want to remove, or is this no longer being removed (as this issue is closed)?