Adobe Global Community

How does Sling resolve an AEM Page to the correct resource type?

Published on by Jörg Hoh on
On the AEM forum there’s an interesting question: Does this mean that all requests to the page node are internally redirected to _jcr_content for HTML and XML calls but not for other extensions ? Without answering the question right here, it raises the question: How is a cq:Page node actually resolved? Or how does Sling know, that it should resolve a call to a cq:Page node to the resourcetype specified in its jcr:content node? Especially since the 'cq:Page' does not have a 'sling:resourceType' property at all?


comments powered by Disqus

Get Insights from the AGC!

Related Posts

Catching up with David Gonzalez
Catching up with David Gonzalez

  Peter Nash