Error : No matching child node definition found for {}header | Community
Skip to main content
P
purvesh47
Level 2
February 7, 2019
Question

Error : No matching child node definition found for {}header

  • February 7, 2019
  • 1 reply
  • 1843 views

Error : Failed publishing path=/apps/att/components/structure/header, result=JcrResult[ success:false, exception: org.apache.sling.ide.transport.RepositoryException - javax.jcr.nodetype.ConstraintViolationException: no matching child node definition found for {}header]

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

1 reply

Gaurav-Behl
Gaurav-Behl
Level 10
February 7, 2019

What steps did you perform that resulted in this error?

Did you try to sync CRX/local using AEM Dev tools?

Could you validate that

  • the node paths exists for header, structure?
  • the node type is correct for header, structure?
  • filter.xml doesn't have any constraints or ambiguous entries?

pls. share more details so that its easier to debug.

Refer Error when publishing changes in the apps / content project from workspc to the local AEM instance  · Issue #1 · Adobe-M…

Terms & ConditionsAccessibility statement

Loading footer...