Repository navigation
CXF-8156 - Include the matched JAX-RS resource operation in fault log… - #3608
Merged
Merged
Conversation
reta
approved these changes
Oct 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
… 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