According to the current documentation being changed within this pull request, OSGi configuration for JCRNodeChangeEventHandler should have in its name the following FQCN incorporated: com.adobe.acs.commons.httpcache.store.mem.impl.JCRNodeChangeEventHandler. That istruction is wrong, because a class with such FQCN doesn't exist and the real FQCN for JCRNodeChangeEventHandler is com.adobe.acs.commons.httpcache.invalidator.event.JCRNodeChangeEventHandler. An OSGi configuration created according to the current version of documentation has no relevant effect and the configuration isn't recognized as a valid one for JCRNodeChangeEventHandler.
This pull request fixes the discrepancy described above via adjustment of the documentation so that it points at the real FQCN of JCRNodeChangeEventHandler, i.e. via the replacement of com.adobe.acs.commons.httpcache.store.mem.impl.JCRNodeChangeEventHandler with com.adobe.acs.commons.httpcache.invalidator.event.JCRNodeChangeEventHandler.
There is an HTTP Cache feature in the ACS AEM Commons Library (https://adobe-consulting-services.github.io/acs-aem-commons/features/http-cache/index.html).
HTTP Cache feature provides a configurable
JCRNodeChangeEventHandlerOSGi component.Fully-qualified class name (FQCN) of
JCRNodeChangeEventHandleriscom.adobe.acs.commons.httpcache.invalidator.event.JCRNodeChangeEventHandler(https://github.com/Adobe-Consulting-Services/acs-aem-commons/blob/master/bundle/src/main/java/com/adobe/acs/commons/httpcache/invalidator/event/JCRNodeChangeEventHandler.java). Therefore, OSGi configuration for the component should have in its name the mentioned FQCN incorporated.According to the current documentation being changed within this pull request, OSGi configuration for
JCRNodeChangeEventHandlershould have in its name the following FQCN incorporated:com.adobe.acs.commons.httpcache.store.mem.impl.JCRNodeChangeEventHandler. That istruction is wrong, because a class with such FQCN doesn't exist and the real FQCN forJCRNodeChangeEventHandleriscom.adobe.acs.commons.httpcache.invalidator.event.JCRNodeChangeEventHandler. An OSGi configuration created according to the current version of documentation has no relevant effect and the configuration isn't recognized as a valid one forJCRNodeChangeEventHandler.This pull request fixes the discrepancy described above via adjustment of the documentation so that it points at the real FQCN of
JCRNodeChangeEventHandler, i.e. via the replacement ofcom.adobe.acs.commons.httpcache.store.mem.impl.JCRNodeChangeEventHandlerwithcom.adobe.acs.commons.httpcache.invalidator.event.JCRNodeChangeEventHandler.