You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 26, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Feb 26, 2023. It is now read-only.
The idea is that it's annoying to remember that RestClient throws Runtime Exceptions when there's either a JSON parsing problem or a problem with the server connection/response.
adding compile errors to the annotated @Rest interfaces if they do not declare throwing the right checked exception
and therefore breaking backward compatibility on all @Rest interfaces
Having to recreate exceptions corresponding to the already existing unchecked ones in the implementation frameworks
Having to catch these runtime exceptions in the generated code and throw wrapping checked exceptions instead, leading to and additional layer in the stacktrace.
Maybe there's a good reason why Spring RestTemplate made these exceptions unchecked :)
Follow up for the discussion on the mailing list
The idea is that it's annoying to remember that RestClient throws Runtime Exceptions when there's either a JSON parsing problem or a problem with the server connection/response.