"components" folder is empty in CRX Lite | Community
Skip to main content
doriguetto
doriguetto
Level 2
October 16, 2015
Solved

"components" folder is empty in CRX Lite

  • October 16, 2015
  • 2 replies
  • 615 views

Hi,

I got a weird problem here, my "components" folder is empty in CRX Lite however i can see the whole jcr structure using JCR Content Explorer. All pages are working fine so i'm assuming the nodes / structures are  there.

My project is maven based and i didnt find any POM or XML inconsistence and no exceptions as well. Any clues what may be the problem?

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

When you have done a check on the page, for which you don't find any components but it loads fine, then use the "Recent requests" tool of the Felix console (http://localhost:4502/system/console/requests) and select your request there (maybe you need to repeat it, by default only the last 20 requests to the instance are listed there). Then the path of all used components is displayed (if they are in fact cq:Component nodes and no servlets).

Jörg

2 replies

joerghoh
Adobe Employee
joerghohAdobe EmployeeAccepted solution
Adobe Employee
October 16, 2015

When you have done a check on the page, for which you don't find any components but it loads fine, then use the "Recent requests" tool of the Felix console (http://localhost:4502/system/console/requests) and select your request there (maybe you need to repeat it, by default only the last 20 requests to the instance are listed there). Then the path of all used components is displayed (if they are in fact cq:Component nodes and no servlets).

Jörg

doriguetto
doriguettoAuthor
Level 2
October 16, 2015

Hi, i can confirm (from requests console) that sling is resolving all the components correctly to my "component" tree, however the "components" tree is appearing empty in CRXDE Lite. On the other hand Content Explorer display the "component" tree correctly.

Terms & ConditionsAccessibility statement

Loading footer...