cannot render resource SyntheticResource, | Community
Skip to main content
sreedobe
Level 4
July 31, 2020
Solved

cannot render resource SyntheticResource,

  • July 31, 2020
  • 3 replies
  • 1790 views

I have jsp based components on AEM 6.5, which have <cq:include> to resourceType that exists in code.

 

I am not sure why I am seeing in error logs. any suggestions, why this could happen, I know , it is a content node that does not exist, as path="fakepath" , resourceType="path to component" .

org.apache.sling.servlets.get.impl.DefaultGetServlet No renderer for extension html, cannot render resource SyntheticResource,

 Could not find much help on "synthertic resource" Thanks.

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 Vaibhavi_J

Hi @sreedobe , 

 

Please check the below thread where similar issue is addressed and resolved. 

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/no-renderer-for-extension-html-cannot-render-resource-in-sites/qaq-p/215967

3 replies

Vaibhavi_J
Vaibhavi_JAccepted solution
Level 7
July 31, 2020
vanegi
Adobe Employee
Adobe Employee
July 31, 2020

Hi @sreedobe,

This error occurs when the node in the /content tree does not have a resourceType property. Or the resourceType does not exist. 

 

Quick checkpoint:-

ChitraMadan
Community Advisor
Community Advisor
July 31, 2020

Hi @sreedobe ,

 

I encountered the same logs and the reason found was there was a resource which was getting included from the templatepage and which did not exist.

Something like below:

templatepage/body.jsp

<body
<cq:include script="version.jsp" />
</body>
version.jsp
<cq:include path="version" resourceType="/apps/sampleapp/components/version" />  -  Non existent resource
So all the pages using this template was throwing this error - org.apache.sling.servlets.get.impl.DefaultGetServlet No renderer for extension html, cannot render resource SyntheticResource
I would suggest to find the references of problematic resource, it must be getting included from somwhere with <cq:include>