Yegor Kozlov created JCR-4935:
---------------------------------
Summary: session.exportDocumentView() generates unparsable XML if
a JCR Property contains invalid XML character
Key: JCR-4935
URL: https://issues.apache.org/jira/browse/JCR-4935
Project: Jackrabbit Content Repository
Issue Type: Bug
Components: core
Affects Versions: 2.21.17
Reporter: Yegor Kozlov
Attachments: image-2023-05-29-14-58-05-591.png
I came across this issue in AEM, where user content can contain all kinds of
special characters. In my case it was a 0x3 character (^C) in a node property
which was written in the JCR XML as-is, and it resulted in a unparsable output.
!image-2023-05-29-14-58-05-591.png|width=968,height=305!
IMO control characters, non-characters and out-of-unicode-range characters
should be skipped when writing XML. These can come from user data and can act
as a "poison pill" breaking the export/import functionality.
The PR is coming.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
