[grpc-io] [grpc-java] global exception handler on client-side

With grpc 0.15.0 some time ago I implemented client side exception handler via spring aspect. It converts StatusRuntimeException from the upstream service into my own domain exception and re-throws it. I find it quite convenient as throughout the code I can catch particular exceptions I'm inter

[grpc-io] Re: [grpc-java] global exception handler on client-side

I have 1-2 channels and 1-12 stubs in 5 applications. Subs have up to 30 methods, so I don't really consider writing wrappers manually as a viable option. > Why not just do the conversion in an interceptor? I'd be happy to know how. As far as I can see all interceptor methods(except cancel) can

[grpc-io] Re: [grpc-java] global exception handler on client-side

Hi! Any updates on this? I checked version 1.9.0 and still don't see a way to do exception conversion in an interceptor. I now think of writing my own wrappers for all blocking stubs to perform exception conversion. That would allow not to check status codes across the application and just ca

[grpc-io] Re: [grpc-java] global exception handler on client-side

Here's the example that shows what I'm trying to achieve - https://github.com/cartmanez/grpc-java-by-example/tree/master/error-handling-example The idea is the following: I have a set of domain exception known by each microservice. There's a mapping domain exception <-> StatusRuntimeException Se

[grpc-io] Re: [grpc-java] global exception handler on client-side

Carl, thanks for reply. However, I'm a bit confused as I don't see a way to return my custom exception from the listener to the calling code. Throwing an exception from onClose simply swallows the exception and makes the call hang forever. super.onClose() only accepts status and trailers. So, n

[grpc-io] Re: [grpc-java] global exception handler on client-side

This is exactly what I'm trying to avoid - unwrapping StatusRuntimeException each time I expect an exception or each time I call a grpc stub method. What I want is to setup an exception converter once, and have it applied automatically to all grpc calls. On Thursday, March 29, 2018 at 7:00:07 P

Re: [grpc-io] Re: [grpc-java] global exception handler on client-side

Is ClientCalls class part of public API? I.e. am I safe to assume that it won't have breaking changes as long as I'm using grpc 1.X? -- CONFIDENTIALITY NOTICE: This email and files attached to it are confidential. If you are not the intended recipient you are hereby notified that using, copy

Re: [grpc-io] Re: [grpc-java] global exception handler on client-side

Thanks! On Friday, January 11, 2019 at 4:39:53 AM UTC+3, Kun Zhang wrote: > > Yes it's public API and we guarantee it won't break within the same major > version. > > On Thursday, January 10, 2019 at 12:13:52 AM UTC-8, eval...@exadel.com > wrote: >> >> Is ClientCalls class part of public API? I.