The most common example of this issue is when the ServiceNotFoundException is thrown. The stack trace will show where the invoker was called (typically the framework), rather than where in the application code requested the service.
It would be really useful to either change the stack trace in the exception, or provide some kind of context to the exception's message of what file/function/line originally triggered the invoker.
The most common example of this issue is when the
ServiceNotFoundExceptionis thrown. The stack trace will show where the invoker was called (typically the framework), rather than where in the application code requested the service.It would be really useful to either change the stack trace in the exception, or provide some kind of context to the exception's message of what file/function/line originally triggered the invoker.