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 has been archived by the owner on May 28, 2018. It is now read-only.
At the moment the only possibility to catch an exception (that is caused by for example a timeout or an exception in a ClientRequestFilter) is to wrap the client itself in a try/catch block.
It would be helpful if for an existing client an exception handler could be registered.
This is for instance required if you want to trace the requests and responses. In the Happy Path scenario a trace can be started in ClientRequestFilter and stopped in ClientResponseFilter. In case of an exception the trace cannot be stopped.
An alternative could be an Interceptor. WriterInterceptor cannot be used as it only is called if there is a payload.
The text was updated successfully, but these errors were encountered:
At the moment the only possibility to catch an exception (that is caused by for example a timeout or an exception in a
ClientRequestFilter
) is to wrap the client itself in atry/catch
block.It would be helpful if for an existing client an exception handler could be registered.
This is for instance required if you want to trace the requests and responses. In the Happy Path scenario a trace can be started in
ClientRequestFilter
and stopped inClientResponseFilter
. In case of an exception the trace cannot be stopped.An alternative could be an Interceptor.
WriterInterceptor
cannot be used as it only is called if there is a payload.The text was updated successfully, but these errors were encountered: