[SLING-9344] Sling CMS - Namespace for nodes is wrong in nodetypes.cnd

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: App CMS 0.10.0
• Fix Version/s: App CMS 0.16.2
• Component/s: App CMS
• Environment: Hardware does not matter, I assume - but I did test on two different macs with Amazon Corretto 8 as JDK.
• Assignee: Dan Klco
• Reporter: Matthias Herold
• Created: 08/Apr/20 16:18
• Updated: 20/Apr/20 14:31
• Resolved: 09/Apr/20 03:52

Description

The namespace specified in the file ui/src/main/resources/SLING-INF/nodetypes/nodetypes.cnd of repository sling-org-apache-sling-app-cms is wrong.

Line 24 reads: <sling = 'http://www.sling.apache.org/sling/1.0'>

This should be: <sling = 'http://sling.apache.org/jcr/sling/1.0'> 

This is a major issue when creating new repositories: when you build a custom starter package including Apache CMS and create a new repository with this starter package afterwards, the namespace of all nodes in the repository is automatically wrong. In normal operation, you won't notice that. But when you export content as package from a sling instance with the right namespace and import the content to a sling instance with the wrong namespace the import will fail. I did not test the other way round, but assume the issue also occurs there. 

Suggested fix: change

http://www.sling.apache.org/sling/1.0

to 

http://sling.apache.org/jcr/sling/1.0

in sling-org-apache-sling-app-cms/ui/src/main/resources/SLING-INF/nodetypes/nodetypes.cnd

Issue Links

• Blocked: SLING-9012 Unkown nodetype during package installation