[SLING-10931] CPConverter - Sling initial content - json files should be converted to folders with a content xml in any case to avoid conflicts

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Content-Package to Feature Model Converter 1.1.10
• Fix Version/s: Content-Package to Feature Model Converter 1.1.12
• Component/s: Content-Package to Feature Model Converter
• Assignee: Niek Raaijmakers
• Reporter: Niek Raaijmakers
• Created: 19/Nov/21 04:38
• Updated: 27/Jun/22 08:16
• Resolved: 17/Jan/22 16:16

Description

In case of converting sling initial content containing JSON files over to xml, currently the cpconverter simply creates a xml file in the same level.

The problem is when there are other files in a directory with the same name to go along the resourceType.

For example we have:

 

• page.json
• page/body.html
• page/footer.html

 

The result will be:

• page.xml
• page/body.html
• page/footer.html

 

Vault doesn't like this approach so much, resulting in stuff like:

• page.dir
• page.xml
• page/.content.xml (with resourceType nt:folder)
• page/body.html
• page/footer.html

The solution lies in simply redirecting the output to .content.xml in a new folder:

• page/.content.xml 
• page/body.html
• page/footer.html

 

Issue Links

• is cloned by: SLING-11058 CPConverter - sling initial content - check illegal xml chars
• is related to: SLING-11420 Remove unused classes for DocView serialization