Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

What all node types support child node ordering in aem?

Avatar

Level 5

Hi Guys,

What all NodeType supports child node ordering, so I can use Node.orderBefore() method on that? Is there any way to make any Node type orderable?

Thanks!

Rashid Jorvee

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

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

View solution in original post

2 Replies

Avatar

Correct answer by
Community Advisor

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