JCR content structure - cq:Page with cq:Page child
Good day,
I've come across a rather "odd" structure in the content tree of my current project. One of the pages under /content has another page in it's jcr:content node. This child page has it's own jcr:content node. So it looks like this:
/content/myPage (jcr:primaryType: cq:Page)
/content/myPage/parsys (jcr:primaryType: nt:unstructured, sling:resourceType: foundation/component/parsys)
/content/myPage/parsys/jcr:content (jcr:primaryType: nt:unstructured)
/content/myPage/parsys/jcr:content/mySubPage (jcr:primaryType: cq:Page)
/content/myPage/parsys/jcr:content/mySubPage/jcr:content (jcr:primaryType: nt:unstructured)
/content/myPage/parsys/jcr:content/mySubPage/jcr:content/parsys (jcr:primaryType: nt:unstructured, sling:resourceType: foundation/component/parsys)
The whole page is rendered properly (both in the author and publisher environments), with the content of the mySubPage node showing at the right place on the myPage.
I've never seen this kind of structure, so I have some concerns. Is there any objection to having this kind of content structure?
Thanks!