[CXF-7996] Fix @Encode TCK test
#778
Merged
Conversation
This file contains 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
Signed-off-by: Andy McCright <j.andrew.mccright@gmail.com>
reta
approved these changes
Apr 15, 2021
|
Thank you @andymc12 ! |
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.
This should fix the following Jakarta RESTful WS TCK failures:
The issue is that (prior to this fix) form parameters are read into a map as either decoded or encoded based on whether the first parameter has the
@Encodedannotation or not. This can result in the@Encodedannotation on second or subsequent parameters getting ignored.The fix is to read the parameters into the map without performing any decoding until it is determined which parameters should be decoded.