You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Seifert (Jira)" <ji...@apache.org> on 2023/02/24 09:55:00 UTC

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

Stefan Seifert created SLING-11785:
--------------------------------------

             Summary: cpconverter: Sling-Initial-Content String values are not properly escaped in DocView XML
                 Key: SLING-11785
                 URL: https://issues.apache.org/jira/browse/SLING-11785
             Project: Sling
          Issue Type: Bug
          Components: Content-Package to Feature Model Converter
    Affects Versions: Content-Package to Feature Model Converter 1.3.0
            Reporter: Stefan Seifert
             Fix For: Content-Package to Feature Model Converter 1.3.2


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|https://github.com/stefanseifert/aem-cloud-service-deployment-issues/commit/866fab64b6280c213e93dbbe5c9791f1a9877f5b] 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.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)