Adobe Experience Manager: How to clear the cache of HTL/JSP/JS/CSS for custom components
When you modify HTL/JSP/JS/CSS files for your custom component, AEM might not immediately reflect the modifications to the pages with the component. The internal cache must be the reason, this article will help you understand how to clear the cache for these files.
Description description
Environment
Experience Manager 6.5
Issue/Symptoms
When you modify HTL/JSP/JS/CSS files for the custom components, AEM might not immediately reflect the modifications to the pages with the component. In this case, the internal cache may be a cause.
Learn how to clear the cache of these files.
Resolution resolution
You can clear the cache by the following functions:
-
Client Libraries: JS/CSS files
Rebuild Client Libraries > Invalidate Caches or Rebuild Libraries
http://localhost:4502/libs/granite/ui/content/dumplibs.rebuild.html
-
File System Class Loader: JSP, HTL
Web Console > Sling > File System Class Loader > Clear Class Loader
http://localhost:4502/system/console/fsclassloader
-
Script Cache: HTL, JS file
Web Console > Sling > Script Cache Status > Clear Cache
http://localhost:4502/system/console/scriptcache
It is recommended to perform clearing the cache at a quiet time to avoid performance degradation.
You may need to check the dispatcher cache and browser cache, also.