Jackrabbit- Property is not allowed in node with potential default types [nt:folder] | Community
Skip to main content
Mario248
Mario248
Level 7
December 2, 2022
Solved

Jackrabbit- Property is not allowed in node with potential default types [nt:folder]

  • December 2, 2022
  • 4 replies
  • 5187 views

I am trying to build a workflow model in AEMaaCS but it failed to build the code with below errors, but the same is working in my local AEM SDK without having any error. 

 

I'm not sure if cloud instance expects nt:folder instead of nt:unstructure. Does anyone have experience with a similar problem?

 

13:40:53,475 [main] [ERROR] ValidationViolation: "jackrabbit-nodetypes: Property 'cq:template' [String] is not allowed in node with potential default types [nt:folder]: No applicable property definition found for name and type!", filePath=jcr_root/conf/global/settings/models/Review-Document/.content.xml, nodePath=/conf/global/settings/models/Review-Document/jcr:content, line=12, column=58


13:40:53,478 [main] [ERROR] ValidationViolation: "jackrabbit-nodetypes: Property 'jcr:title' [String] is not allowed in node with potential default types [nt:folder]: No applicable property definition found for name and type!", filePath=jcr_root/conf/global/settings/models/Review-Document/.content.xml, nodePath=/conf/global/settings/models/Review-Document/jcr:content, line=12, column=58

 

13:40:53,482 [main] [ERROR] ValidationViolation: "jackrabbit-nodetypes: Property 'cq:lastModified' [Date] is not allowed in node with potential default types [nt:folder]: No applicable property definition found for name and type!", filePath=jcr_root/conf/global/settings/models/Review-Document/.content.xml, nodePath=/conf/global/settings/models/Review-Document/jcr:content, line=12, column=58

 

13:40:53,487 [main] [ERROR] ValidationViolation: "jackrabbit-nodetypes: Property 'cq:lastModifiedBy' [String] is not allowed in node with potential default types [nt:folder]: No applicable property definition found for name and type!", filePath=jcr_root/conf/global/settings/models/Review-Document/.content.xml, nodePath=/conf/global/settings/models/Review-Document/jcr:content, line=12, column=58

 

13:40:53,488 [main] [ERROR] ValidationViolation: "jackrabbit-nodetypes: Property 'sling:resourceType' [String] is not allowed in node with potential default types [nt:folder]: No applicable property definition found for name and type!", filePath=jcr_root/conf/global/settings/models/Review-Document/.content.xml, nodePath=/conf/global/settings/models/Review-Document/jcr:content, line=12, column=58

 

13:40:53,489 [main] [ERROR] ValidationViolation: "jackrabbit-nodetypes: Property 'lastSynced' [Date] is not allowed in node with potential default types [nt:folder]: No applicable property definition found for name and type!", filePath=jcr_root/conf/global/settings/models/Review-Document/.content.xml, nodePath=/conf/global/settings/models/Review-Document/jcr:content, line=12, column=58

 

13:40:53,490 [main] [ERROR] ValidationViolation: "jackrabbit-nodetypes: Property 'cq:designPath' [String] is not allowed in node with potential default types [nt:folder]: No applicable property definition found for name and type!", filePath=jcr_root/conf/global/settings/models/Review-Document/.content.xml, nodePath=/conf/global/settings/models/Review-Document/jcr:content, line=12, column=58

 

13:40:53,490 [main] [ERROR] ValidationViolation: "jackrabbit-filter: Node '/conf/global/settings/models/Review-Document/jcr:content/flow' is not contained in any of the filter rules", filePath=jcr_root/conf/global/settings/models/Review-Document/.content.xml, nodePath=/conf/global/settings/models/Review-Document/jcr:content/flow, line=15, column=63

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 aanchal-sikka

Hello,

Folder "/conf/global/settings/workflow/models" and sub-folders should be of type "sling:Folder".

And I guess "Review-Document" is a Workflow Model. In this case, please check its "jcr:primaryType". It should be "cq:Page".

The errors that you have mentioned often occur when we do not have proper jcr:primaryType deployed via code.

In case of local, we often edit via UI, and AEM assures that proper types are created for the parent node and the current one.

Thus, when we deploy to server, we need to take care of filters in our code. The hierarchy and the "Review-Document" should deploy expected node types.

4 replies

V
VeenaK
Level 4
December 2, 2022

Hi @mario248

It is because of the jackrabbit version issue, could you please update the dependency of the jackrabbit validator in the pom and try to built it, that should resolve the issue.

https://issues.apache.org/jira/browse/JCRVLT-489

Please refer above thread for more information.

    Mario248
    Mario248Author
    Level 7
    December 2, 2022

    Sorry, I don't see any solution on the above ticket. Could you please let me know which jackrabbit validator I should use in my pom file? Any sample code snippets ?

     
      krati_garg
      Adobe Employee
      krati_gargAdobe Employee
      Adobe Employee
      December 2, 2022

      @mario248

      Shouldn't this be

      /conf/global/settings/workflow/models/Review-Document/

      instead of

      /conf/global/settings/models/Review-Document/

      Please check

        Sachin_Arora_
        Community Advisor
        Sachin_Arora_Community Advisor
        Community Advisor
        December 3, 2022

        Hi @mario248 : Warnings looks valid as nt:folder node is not allowed to have property like jcr:title. Please remove the invalid properties from .content.xml and build would work fine.

        Please refer this screenshot on how warning is coming if I manually try to add property jcr:title on nt:folder node.

          aanchal-sikka
          Community Advisor
          aanchal-sikkaCommunity AdvisorAccepted solution
          Community Advisor
          December 3, 2022

          Hello,

          Folder "/conf/global/settings/workflow/models" and sub-folders should be of type "sling:Folder".

          And I guess "Review-Document" is a Workflow Model. In this case, please check its "jcr:primaryType". It should be "cq:Page".

          The errors that you have mentioned often occur when we do not have proper jcr:primaryType deployed via code.

          In case of local, we often edit via UI, and AEM assures that proper types are created for the parent node and the current one.

          Thus, when we deploy to server, we need to take care of filters in our code. The hierarchy and the "Review-Document" should deploy expected node types.

          Aanchal Sikka
            Terms & ConditionsAccessibility statement

            Loading footer...