AEM 6/JCR3 | Community
Skip to main content
A
atrissel
October 16, 2015
Solved

AEM 6/JCR3

  • October 16, 2015
  • 1 reply
  • 619 views

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?

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 JustinEd3

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

1 reply

J
Adobe Employee
JustinEd3Adobe EmployeeAccepted solution
Adobe Employee
October 16, 2015

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

Terms & ConditionsAccessibility statement

Loading footer...