Upgrading Namespaces

Upgrading your project to a CMS 7 version that uses newer basic Hippo JCR namespaces. Preventing work in future upgrades.

For Hippo JCR namespaces, the URL identifying a namespace contains a version number. Therefor, when the version changes,  the namespace declaration changes.

A newer version of CMS 7 may use newer versions of basic Hippo JCR namespaces, so if you upgrade your CMS project to use a newer version of CMS 7, you  may have to change some namespace declarations in your project.

Namespace declarations for basic Hippo JCR namespaces always occur in your CND files and they may occur in your content and/or configuration XML files. You may remove them from the XML files savely, to prevent having to upgrade them.

 

In your project you probably have some content and/or configuration XML files that are imported via your hippoecm-extension.xml.  If you use XML files that you exported from the web console, they contain XML declarations for unused XML namespaces, as the JCR namespaces are declared as XML namespaces, conforming to the JCR specification. As the JCR namespaces are not actually used as XML namespaces, their XML declarations are not necessary for valid XML, so you can remove them safely.

 

If for some reason you do not want to remove them, you have to change the declarations in all XML files when you upgrade to a CMS 7 version that uses a newer version for one or more of the basic Hippo JCR namespaces.