How to Validate JSP Compilation after Package Installation

[Thomas_H77]

Other than manually running all of the templates/pages/components etc.. is there any built in mechanism within CQ 5.5 or AEM 6.1 to verify that all the code was properly compiled after a package has been installed?

[edubey]

AFAIK, there is not OOTB way.

But at least you can ensure by checking the status of bundle, once installed to ensure it met all its dependencies and in running state.

[smacdonald2008]

It is assumed before you install a package on production - you test it in your locale Dev environment and make sure all the script is working and there is no compile errors.  Then after you deploy on production - you test again. 

CQ does not have a way to automatically test whether code compiles after you install the package. 

[Thomas_H77]

smacdonald2008 wrote...

It is assumed before you install a package on production - you test it in your locale Dev environment and make sure all the script is working and there is no compile errors.  Then after you deploy on production - you test again. 

CQ does not have a way to automatically test whether code compiles after you install the package. 

Yes, the code is always tested internally what I'm referring to are instances where we install a package on multiple Publish servers and for 1 of the servers JSP #### doesn't properly compile, and we have to manually delete it under /var/classes/.... and restart the JSP bundles to regenerate the file.

I'm not talking about code not properly compiling.

[smacdonald2008 · Accepted solution]

Here is a KB that may help:

https://helpx.adobe.com/experience-manager/kb/CQ5JSPsNotRecompilingOnPackageInstallation.html

There is no other tool out of the box to help in this use case. Hope this helps. 

[Thomas_H77]

Thanks this should provide enough information to satisfy Management.

[Kunal_Gaba_]

smacdonald2008 wrote...

Here is a KB that may help:

https://helpx.adobe.com/experience-manager/kb/CQ5JSPsNotRecompilingOnPackageInstallation.html

There is no other tool out of the box to help in this use case. Hope this helps. 

This won't work for AEM 6.1 as compiled JSPs classes are no more stored in /var/classes. They are instead stored on the file system on which AEM runs.