Expand my Community achievements bar.

Guidelines for the Responsible Use of Generative AI in the Experience Cloud Community.
SOLVED

AEM 6/JCR3

Avatar

Level 1

In AEM 5.6.1 duplicate node names at the same level were given unique names automatically

node1     =>           node1    

    html       =>         html

    html       =>         html[1]

This is not true in AEM 6. If you programmitically create the same node structure, you will get a duplicate node exception.  It seems that JCR3 does not automatically unique names. Is this by design? It is a difference in versions, and is compelling me to rewrite a bunch of code.  Is there a system setting that could adjust this?

1 Accepted Solution

Avatar

Correct answer by
Employee

Hi,

This is by design. Oak does not support Same Name Siblings. They were always discouraged: http://wiki.apache.org/jackrabbit/DavidsModel#Rule_.234:_Beware_of_Same_Name_Siblings.

If you need SNS on AEM 6, you will need to run with CRX2, not Oak.

Regards,

Justin

View solution in original post

1 Reply

Avatar

Correct answer by
Employee

Hi,

This is by design. Oak does not support Same Name Siblings. They were always discouraged: http://wiki.apache.org/jackrabbit/DavidsModel#Rule_.234:_Beware_of_Same_Name_Siblings.

If you need SNS on AEM 6, you will need to run with CRX2, not Oak.

Regards,

Justin