I am trying to use the Ensure Oak Index tool to create a new index. I created the new index from the index suggested by Oak Index Definition Generator. In the generated index, one of the JCR Nodes is named dam:Asset
Following the instructions for Ensure Oak Index, I am trying to deploy the index as code as a part of my build pipeline. Whenever I build the project, the node in my index is renamed from dam:Asset to dam0:Asset Can anyone tell me why? How can I deploy my index code via pipeline if I am not allowed to use that node name. The index does not work if the node is not named dam:Asset. On the right is the source .content.xml for my index. And on the left is what is being changed after during the package install. The built package is correct.
Solved! Go to Solution.
Thank you for the suggestion. It was not quite the right answer, but it did point me in the right direction. The problem and solution was the jcr:root node of my index:
There was another object in our code repo that also was declaring a namespace for dam objects that used a different path "xmls:dam="https://www.jsp.org/jcr/dam/1.0" Once I made these two namespace declarations match, the system stopped renaming "dam:Asset" to "dam0:Asset".