[PR] CXF-8156 - Include the matched JAX-RS resource operation in fault log… [cxf]

["coheigea (via GitHub)" <gi...@apache.org>]

coheigea opened a new pull request, #3608:
URL: https://github.com/apache/cxf/pull/3608

   … messages
   
   When a service throws an exception, CXF logs Application '<service name>' has thrown exception. In a JAX-RS server with several resource classes and no serviceName set, that name is always the first resource class. So the log often points at the wrong resource, and it never says which method failed.
   
   The service name has to stay fixed for the whole server, because the endpoint and JMX names also use it. So the fix leaves the name alone and adds the method that actually handled the request. JAX-RS already records that method on the request context (exchange); the logging code now reads it when no SOAP operation is available.
   
   Before: Application '{ns}FirstResource' has thrown exception
   After: Application '{ns}FirstResource#SecondResource#getItem' has thrown exception


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@cxf.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [PR] CXF-8156 - Include the matched JAX-RS resource operation in fault log… [cxf]

["coheigea (via GitHub)" <gi...@apache.org>]

coheigea merged PR #3608:
URL: https://github.com/apache/cxf/pull/3608


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@cxf.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org