"_cq_editConfig.xml" is throwing a SAX parse exception in CQ 6.1 | Adobe Higher Education
Skip to main content
K
kallada_san
Level 2
October 16, 2015
Resuelto

"_cq_editConfig.xml" is throwing a SAX parse exception in CQ 6.1

  • October 16, 2015
  • 17 respuestas
  • 3881 visualizaciones

Hi,

While trying to install component which was created for 5.6  is throwing an error an exception in CQ 6.1. Please find the trace below.

    18.09.2015 09:07:19.868 *ERROR* [qtp383669503-68] org.apache.jackrabbit.vault.fs.impl.io.GenericArtifactHandler Error while parsing jcr_root/apps/my-foundation/components/content/events/myCalendar/_cq_editConfig.xml: {}
org.xml.sax.SAXException: null
    at org.apache.jackrabbit.vault.fs.impl.io.DocViewSAXImporter.startElement(DocViewSAXImporter.java:653)
    at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(Unknown Source)
    at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
    at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl$NSContentDriver.scanRootElementHook(Unknown Source)
    at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(Unknown Source)
    at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(Unknown Source)
    at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(Unknown Source)
    at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(Unknown Source)
    at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)

 

And our "_cq_editConfig.xml" looks like :

<?xml version="1.0" encoding="UTF-8"?>
    <jcr:root xmlns:cq="http://www.day.com/jcr/cq/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0"
          cq:actions="[text:myCalendar/_cq_editConfig:,edit,delete]"
          cq:dialogMode="floating"
          cq:disableTargeting="true"
          cq:layout="editbar">
    <cq:listeners
        jcr:primaryType="cq:EditListenersConfig"
        afteredit="REFRESH_PAGE"/>
    </jcr:root>

Any pointers to solve this would be a great help.

 

Thanks and Regards,

Kallada

    Este tema ha sido cerrado para respuestas.
    Mejor respuesta de Kunal_Gaba_

    You are missing primaryType property definition on the root node. Try the below XML and it should work- 

    <?xml version="1.0" encoding="UTF-8"?> <jcr:root xmlns:cq="http://www.day.com/jcr/cq/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0" cq:actions="[text:myCalendar/_cq_editConfig:,edit,delete]" cq:dialogMode="floating" cq:disableTargeting="true" cq:layout="editbar"jcr:primaryType="cq:EditConfig"> <cq:listeners jcr:primaryType="cq:EditListenersConfig" afteredit="REFRESH_PAGE"/> </jcr:root>

    17 respuestas

    Mostrar respuestas anteriores
    K
    kallada_sanAutor
    Level 2
    October 16, 2015

    Hi All,

    Following the SAX parse exception, we are now facing with :

                                          javax.jcr.nodetype.ConstraintViolationException: No matching node definition found for tab_data_source

    in one of our legacy components, Any Idea on this?

    Thanks a lot,

    K
    kallada_sanAutor
    Level 2
    October 16, 2015

    Sorry all, 

    I got it wrong. I'm still getting another form of exception.

    com.day.jcr.vault.packaging.PackageException: org.apache.jackrabbit.vault.packaging.PackageException: javax.jcr.nodetype.ConstraintViolationException: OakConstraint0001: /apps/my-foundation/components/page/detail[[nt:folder]]: No matching definition found for child node tab_data_source with effective type [cq:Dialog]
        at com.day.jcr.vault.packaging.impl.JrVltJcrPackageAdapter.install(JrVltJcrPackageAdapter.java:109)
        at com.day.crx.packaging.impl.J2EEPackageManager.consoleInstall(J2EEPackageManager.java:329)
        at com.day.crx.packaging.impl.J2EEPackageManager.doPost(J2EEPackageManager.java:171)
        at com.day.crx.packaging.impl.PackageManagerServlet.doPost(PackageManagerServlet.java:144)

    Lokesh_Shivalingaiah
    Lokesh_Shivalingaiah
    Level 10
    October 16, 2015

    Check the XML in your 5.6 version. Ideally, primaryType is a default/mandatory property that will have when you create any node !

      K
      kallada_sanAutor
      Level 2
      October 16, 2015

      Thanks kunal, it worked it seems. But these components were perfectly working with 5.6.

      K
      kallada_sanAutor
      Level 2
      October 16, 2015

      Thanks loki, the error thrown while installing is gone now!!!

      Kunal_Gaba_
      Kunal_Gaba_
      October 16, 2015
      That's because the type of page node is "nt:folder". Try changing the nodetype of page node and it should work.
      Lokesh_Shivalingaiah
      Lokesh_Shivalingaiah
      Level 10
      October 16, 2015

      Can you try with this

      <?xml version="1.0" encoding="UTF-8"?>
      <jcr:root xmlns:cq="http://www.day.com/jcr/cq/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0" xmlns:nt="http://www.jcp.org/jcr/nt/1.0"
                jcr:primaryType="cq:Dialog"
                title="Data Source"

                xtype="panel">

          <items jcr:primaryType="cq:WidgetCollection">
              <datasource
                      jcr:primaryType="cq:Widget"
                      collapsed="{Boolean}false"
                      collapsible="{Boolean}false"
                      title="Data Source"
                      xtype="dialogfieldset">
                  <items jcr:primaryType="cq:WidgetCollection">
                      <canonical
                              jcr:primaryType="cq:Widget"
                              fieldLabel="Client Libaries"
                              name="./my-client-libs"
                              xtype="textfield"/>
                      <rootclass
                              jcr:primaryType="cq:Widget"
                              fieldLabel="Root Class"
                              name="./my-root-class"
                              xtype="textfield"/>
                  </items>
              </datasource>
          </items>
      </jcr:root>

        Términos y condicionesAccessibility statement

        Loading footer...