Components with Sightly ; Extension .html Not Rendering the Component | Community
Skip to main content
New Participant
October 16, 2015
Solved

Components with Sightly ; Extension .html Not Rendering the Component

  • October 16, 2015
  • 4 replies
  • 2264 views

I have a component in my code which uses sightly and  script has the extension as .html

So , script of the component would be like : componentName.html

When I try to render the component , I get the following information from the error.log : 

org.apache.sling.servlets.get.impl.DefaultGetServlet No renderer for extension html, cannot render resource Paragraph, path=/content/XXX/Par/Component

Same component is working fine on the Servers. I must be missing some settings / or component from Felix console not running. 

I see the similar issue for all Sightly component.

Any Suggestions I can try ? 

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 joerghoh

Hi,

the string "org.apache.sling.servlets.get.impl.DefaultGetServlet" indicates, that the DefaultGetServlet has taken over. This normally means, that you have a problem in the wiring resource to resourceType. So can you check that your resourceType property on the component node is correct?

kind regards,
Jörg

4 replies

smacdonald2008
New Participant
October 16, 2015

"Same component is working fine on the Servers"

When you say Servers - do you mean the AEM Pub server? 

joerghoh
joerghohAccepted solution
Employee
October 16, 2015

Hi,

the string "org.apache.sling.servlets.get.impl.DefaultGetServlet" indicates, that the DefaultGetServlet has taken over. This normally means, that you have a problem in the wiring resource to resourceType. So can you check that your resourceType property on the component node is correct?

kind regards,
Jörg

New Participant
October 16, 2015

Yes the resource type under the /content/... is a valid one and this is happening only for components with .html (Sightly) extension 

New Participant
October 16, 2015

smacdonald2008 wrote...

"Same component is working fine on the Servers"

When you say Servers - do you mean the AEM Pub server? 

 

 

Its working on all other Environments DEV , QA Etc.

I am getting this error on my localhost 

I am having this issue on Author instance