AEM-6.5.8 - SAX parser exception when installing an index via package manager/build | Community
Skip to main content
N
NitroHazeDev
New Participant
March 9, 2022
Solved

AEM-6.5.8 - SAX parser exception when installing an index via package manager/build

  • March 9, 2022
  • 2 replies
  • 1727 views

Hello Everyone,

 

While trying to install a package with an index , i get the following error .. but exporting it via package manager and importing it works.

Via build process i get the following error 
/oak:index (org.xml.sax.SAXParseException; systemId: file:///C:/Users/......./jcr_root/_oak_index/.content.xml; lineNumber: 964; columnNumber: 68; The prefix "sling" for element "sling:OrderedFolder" is not bound.)



 

 

<custom
jcr:primaryType="oak:QueryIndexDefinition"
async="[async]"
compatVersion="{Long}2"
evaluatePathRestrictions="{Boolean}true"
includedPaths="[/conf/global/settings/dam/adminui-extension/metadataprofile]"
reindex="{Boolean}false"
reindexCount="{Long}6"
type="lucene">
<indexRules jcr:primaryType="nt:unstructured">
<sling:OrderedFolder jcr:primaryType="nt:unstructured">
<properties jcr:primaryType="nt:unstructured">
<jcrTitle
jcr:primaryType="nt:unstructured"
boost="{Long}2"
name="jcr:content/jcr:title"
nodeScopeIndex="{Boolean}true"
propertyIndex="{Boolean}true"
type="String"
useInSpellcheck="{Boolean}true"
useInSuggest="{Boolean}true"/>
</properties>
</sling:OrderedFolder>
</indexRules>
</custom>

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by joerghoh

You need to declare the namespace at the begin of this XML document. You can create a package from a piece of the AEM repository and check the .content.xml files in there to get the right pattern.

2 replies

tb1687196
tb1687196
New Participant
March 13, 2022

Hi @nitrohazedev ,

I am curious to know if you are also seeing the same scenario for other xml's as well?.

    N
    NitroHazeDevAuthor
    New Participant
    March 15, 2022

    @tb1687196 ,not with other files .Looks like when it was first checked in it was missed

      joerghoh
      joerghohAccepted solution
      Employee
      March 11, 2022

      You need to declare the namespace at the begin of this XML document. You can create a package from a piece of the AEM repository and check the .content.xml files in there to get the right pattern.

        N
        NitroHazeDevAuthor
        New Participant
        March 11, 2022

        Yes @joerghoh  that is exactly how i managed to fix it , unfortunately the xml that was checked in did not have the sling: prefix and hence it cried out with errors. 
        Thank you for your assistance as well.

         

          Terms & ConditionsAccessibility statement

          Loading footer...