Skip to main content
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
arunpatidar
arunpatidarAccepted solution
Community Advisor
July 16, 2018

Hi,

The orderable child nodes setting is defined per node type. Whether the child nodes of a node N are orderable depends on the node type of N.

A repository supports orderable child nodes by permitting the registration of node types with an orderable child node setting of true.

When a node does not support orderable child nodes this means that it is left up to the implementation to maintain the order of child nodes. Applications should not, in this case, depend on the order of child nodes returned by Node.getNodes, as it may change at any time. The only exception to this rule is that same-name siblings must maintain their relative order across read method invocations and across sessions.

Please check

JCR 2.0: 23 Orderable Child Nodes (Content Repository for Java Technology API v2.0)

JCR 1.0: 4.4.2 Non-orderable Child Nodes (Content Repository for Java Technology API)

Custom Node Types

Thanks

Arun

Arun Patidar
View in thread

4 replies

arunpatidar
Community Advisor
arunpatidarCommunity AdvisorAccepted solution
Community Advisor
July 16, 2018

Hi,

The orderable child nodes setting is defined per node type. Whether the child nodes of a node N are orderable depends on the node type of N.

A repository supports orderable child nodes by permitting the registration of node types with an orderable child node setting of true.

When a node does not support orderable child nodes this means that it is left up to the implementation to maintain the order of child nodes. Applications should not, in this case, depend on the order of child nodes returned by Node.getNodes, as it may change at any time. The only exception to this rule is that same-name siblings must maintain their relative order across read method invocations and across sessions.

Please check

JCR 2.0: 23 Orderable Child Nodes (Content Repository for Java Technology API v2.0)

JCR 1.0: 4.4.2 Non-orderable Child Nodes (Content Repository for Java Technology API)

Custom Node Types

Thanks

Arun

Translate
Arun Patidar
    smacdonald2008
    smacdonald2008
    Level 10
    July 16, 2018

    Great answer!

    Translate
    david_z
    Level 2
    July 22, 2024

    Hi, we have AEM adaptive forms developed in 6.5.11 and when we need to generate translation and everything worked fine for years. However, when we upgrade to 6.5.16 and need to update the translation, we cannot create translation project anymore and we always get this error;

    com.adobe.aemds.guide.service.impl.GuideLocalizationServiceImpl Child node ordering is not supported on this node

     

    The same form still works fine in 6.5.11 now, and when we upgrade to 6.5.16, we didn't see any instruction on anything need to migrate the existing forms.

    I created new form in 6.5.16 and the translation project can be generated. But I compared my form developed in 6.5.11 and 6.5.16, I cannot find any difference related to Orderable.

    Any idea how to fix this?

     

    Translate
    ancara
    Level 2
    November 12, 2024

    Hello @david_z 

     

    I  have same situation, originally our translations are defined on AEM 6.5.15 and we have to migrate to upper version. How do you solve this error?

    Regards!

    Translate
    Terms & ConditionsAccessibility statement

    Loading footer...