Businesses leveraging the two technologies together would now be able to harness their data for critical insights and predictions, connect customer touchpoints across their business, and drive brand loyalty and growth.
Customers and developers upgrading to AEM 6.0 SP3 will find that there’s a new bundle in use, FSClassLoader. As I described in my previous post this bundle offers superior performance as compared to the repository based classloader, however it does remove the option for developers to access the generated Java code for their JSP’s under
Luckily, when Adobe built AEM 6.0 SP3, they used FSClassLoader version 1.0.2 which includes an OSGi console allowing developers to view the compiled Java files. To view this, open up the OSGi console at http://localhost:4502/system/console and select the console under Sling >> File System Class Loader
From the console you can view or download the compiled .class file, generated .java file or the .deps file which lists the JSP scripts and TagLibs the files depends on.
Hopefully this helps anyone upgrading to AEM 6.0 SP3 and wondering why their generated Java files aren’t appearing under