[SLING-11785] cpconverter: Sling-Initial-Content String values are not properly escaped in DocView XML

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Content-Package to Feature Model Converter 1.3.0
• Fix Version/s: Content-Package to Feature Model Converter 1.3.2
• Component/s: Content-Package to Feature Model Converter
• Assignee: Konrad Windszus
• Reporter: Stefan Seifert
• Created: 24/Feb/23 09:54
• Updated: 08/May/23 15:54
• Resolved: 02/Mar/23 10:27

Description

it seems the cpconverter is not properly escaping string values read from Sling-Initial-Content JSON files and then converting to DocView XML.

in this sample project:
https://github.com/stefanseifert/aem-cloud-service-deployment-issues/tree/feature/archetype-40-DRND-202-escaping
i've introduces in this commit a JSON file in Sling-Initial-Content containing two strings with regexp containing "\". those strings are transferred 1:1 to the DocView XML in the content package, which is wrong. the "\" has to be escaped to be re-read properly via JCR API.

it seems the escaping rules applied by org.apache.jackrabbit.vault.util.DocViewProperty#format are missing.

Issue Links

• is related to: SLING-11421 Use DocView serialisation classes from FileVault
• relates to: JCRVLT-693 Escape values for type javax.jcr.PropertyType.UNDEFINED