Issue :
When there is an exception from grpc services, it appears that the exception is being wrapped with "InvocationTargetException" and the graphql error field contains that one.
Expected Behaviour :
Is there a way that I can suppress "InvocationTargetException" and based on grpc exception, I can rewrite the graphql error fields.
Analysis :
While investigating, the "rejoiner"s "SchemaModule" covers the grpc exception with the "InvocationTargetException" and the graphql "error" fields always has error like below,
"Exception while fetching data (/someGrpcService) : java.lang.reflect.InvocationTargetException"
Tried GraphQl "ExecutionStrategy" to override "graphql.execution.SimpleDataFetcherExceptionHandler" in the "Handler" implementation, but for reason that never gets invoked.
Issue : When there is an exception from grpc services, it appears that the exception is being wrapped with "InvocationTargetException" and the graphql error field contains that one.
Expected Behaviour : Is there a way that I can suppress "InvocationTargetException" and based on grpc exception, I can rewrite the graphql error fields.
Analysis : While investigating, the "rejoiner"s "SchemaModule" covers the grpc exception with the "InvocationTargetException" and the graphql "error" fields always has error like below,
"Exception while fetching data (/someGrpcService) : java.lang.reflect.InvocationTargetException"
Tried GraphQl "ExecutionStrategy" to override "graphql.execution.SimpleDataFetcherExceptionHandler" in the "Handler" implementation, but for reason that never gets invoked.
Any idea how to do the error handling ?