Instead of an AspectJ statically compiled Aspect which weaves the aspect into CAS' DefaultServicesManager and might introduce some surprising weird behavior when reordering the jars in the classloader by renaming cas-addons.jar for example, etc.
The proposed solution gets rid of AspectJ magic and instead relies on the standard Spring's BeanFactoryPostProcessor which will simply destroy 2 quartz beans responsible for invoking the reload method. E.G:
Instead of an AspectJ statically compiled Aspect which weaves the aspect into CAS' DefaultServicesManager and might introduce some surprising weird behavior when reordering the jars in the classloader by renaming cas-addons.jar for example, etc.
The proposed solution gets rid of AspectJ magic and instead relies on the standard Spring's
BeanFactoryPostProcessor
which will simply destroy 2 quartz beans responsible for invoking thereload
method. E.G: