Cxf 9233 fix response context - #3373
Open
vp340 wants to merge 9 commits into
Open
Conversation
…NG_PROP from InMessage into the ResponseContext
…oming from the InMessage
reta
reviewed
Aug 19, 2026
| super(Phase.PRE_INVOKE, sender); | ||
|
|
||
| //Make sure that the LIVE_LOGGING_PROP won't be propagated into the ResponseContext from IN Messages | ||
| addResponseContextExcludedInProperty(LIVE_LOGGING_PROP); |
Member
There was a problem hiding this comment.
@vp340 thanks for another alternative, the problem I see with this one is two fold: LoggingXxxInteceptor has to be aware about the ClientImpl specifics/internals but this is generic feature that works for client (we have many) or/and server (same, many).
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
2 participants
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.
Pull request with a new possible solution to Jira Cxf-9233