split embedded ]]> across CDATA sections when serializing - #903
Open
Sahana2524 wants to merge 1 commit into
Open
split embedded ]]> across CDATA sections when serializing#903Sahana2524 wants to merge 1 commit into
]]> across CDATA sections when serializing#903Sahana2524 wants to merge 1 commit into
Conversation
Sahana2524
force-pushed
the
cdata-end-marker-split
branch
from
August 24, 2026 10:44
7e8f479 to
1a6557d
Compare
🧪 Code Coverage Report
|
1 similar comment
🧪 Code Coverage Report
|
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
1 participant
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.
CDATA values containing
]]>fail to serializeA
@JacksonXmlCDatastring is handed straight towriteCData, and since]]>closes a CDATA section the underlying Woodstox writer rejects it, so any value carrying that sequence cannot be written at all and the round-trip guarantee breaks. The safe form is to split at each]]>(keep the]]in one section, push the>into the next); a coalescing reader, which is the default here, reads the pieces back as the original text. I put the split in a sharedStaxUtil.writeCDatahelper so the plain and pretty-printing paths behave the same.