Hello @jeremylanssiers , Thanks for sharing the solution.

Hello @jeremylanssiers , You can follow this article where each step is described: https://medium.com/@sadyrifat/aem-unit-test-case-for-sling-delegation-pattern-1f011b947fb3  Another GitHub commit link and repo for check your maven dependency also: https://github.com/Sady-Rifat/aem-demo/commit/81ce4...

Hi @AkkiSwami , You can follow this code, In this code I read excel data from DAM and send servlet response into Json. You can modify by your own. JsonNode jsonNode = null; Resource resource = resourceResolver.getResource(damPath); if (resource == null || resource.adaptTo(Ass...

Hello @samsri , You can see this similar thread, https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/com-day-cq-wcm-api-cannot-be-resolved/td-p/385695  If it's not helping you please let me know the following details. Your AEM service pack version and the Uber Jar you are using...

@NitroHazeDev Yes you are right.Actually, from our development perspective, it seems incorrect but according to AEM architecture/concept, this is expected.

Exactly that's the case, When you edit an experience fragment you basically edit a page. (ex: experience fragment page template). On that page, wcmmode behaves as a regular pattern. And you get your desired value.Note: Here I am talking about (/aem/experience-fragments.html/content/experience-fragme...

Hello @NitroHazeDev , See this chart, where the same component is on a page. Once it drops the page directly by parsys, another one comes from XF. This result is from the Slightly. Now, you can question why it happened. The answer is by XF the component is already rendered and comes to the page. Us...

Hello @NitroHazeDev , The answer is related to the author's instance. The Slightly code doesn't detect the wcmmode edit because the XF is rendered from a different path on the page. When you want to use wcmmode edit it's always like/behaves view as publish mode.The Solution is linked to a Model clas...

Hello @NitroHazeDev ,The wcmmode for Experience Fragment on a page differs from its editing mode.There is a similar thread that describes why it behaves like that and how can you get the expected solution: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/when-putting-a-custo...

Hello @vitor45 , Not sure what your script will do, but still from my assumption of some use case you can add your script, If the JS is related to any specific component (except the page component) then you can add this via, <sly data-sly-use.clientlibs="${'com.adobe.cq.wcm.core.components.models.Cl...