Events handlers are not with Page Events when i try to listen on specific paths | Community
Skip to main content
M
Manju73
Level 2
March 4, 2024
Solved

Events handlers are not with Page Events when i try to listen on specific paths

  • March 4, 2024
  • 3 replies
  • 2572 views

When i try to add event filters property for page events .Event handlers are not able to listen to the page events ,But the same code is working with different event topics like resource added ,remove ,changed .When i remove the event filters property its working fine for page events also like page created ,modified ,deleted activities.

The sample code snippet 

@Component(service = .class,
           immediate = true,
        property = {
                EventConstants.EVENT_TOPIC +"=" + PageEvent.EVENT_TOPIC,
                EventConstants.EVENT_FILTER + "=(path=/content/trainingproject/en_us/*)"
        }
)
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by arunpatidar

It will execute every page related event but we can filter page creation events from page modifications object but the real problem it will listen to all the pages. We have nearly 5000+pages in prod. If that is the case it will trigger on every page related events. Is there any possibility to listen events in certain paths with jcr event listener. If it is possible then I will use jcr event listener. 


Is there any possibility to listen events in certain paths with jcr event listener. If it is possible then I will use jcr event listener.  Yes, you can

 

public void addEventListener(EventListener listener, int eventTypes, java.lang.String absPath, boolean isDeep, java.lang.String[] uuid, java.lang.String[] nodeTypeName, boolean noLocal) throws RepositoryException

 

Adds an event listener that listens for the specified eventTypes (a combination of one or more event types encoded as a bit mask value).

The set of events can be filtered by specifying restrictions based on characteristics of the node associated with the event. In the case of event types NODE_ADDED and NODE_REMOVED, the node associated with an event is the node at (or formerly at) the path returned by Event.getPath. In the case of event types PROPERTY_ADDED, PROPERTY_REMOVED and PROPERTY_CHANGED, the node associated with an event is the parent node of the property at (or formerly at) the path returned by Event.getPath:

  • absPath, isDeep: Only events whose associated node is at absPath (or within its subtree, if isDeep is true) will be received. It is permissible to register a listener for a path where no node currently exists.
  • uuid: Only events whose associated node has one of the UUIDs in this list will be received. If his parameter is null then no UUID-related restriction is placed on events received.
  • nodeTypeName: Only events whose associated node has one of the node types (or a subtype of one of the node types) in this list will be received. If his parameter is null then no node type-related restriction is placed on events received.

The restrictions are "ANDed" together. In other words, for a particular node to be "listened to" it must meet all the restrictions.

Additionally, if noLocal is true, then events generated by the session through which the listener was registered are ignored. Otherwise, they are not ignored.

The filters of an already-registered EventListener can be changed at runtime by re-registering the same EventListener object (i.e. the same actual Java object) with a new set of filter arguments. The implementation must ensure that no events are lost during the changeover.

 

Parameters:
listener - an EventListener object.
eventTypes - A combination of one or more event type constants encoded as a bitmask.
absPath - an absolute path.
isDeep - a boolean.
uuid - array of UUIDs.
nodeTypeName - array of node type names.
noLocal - a boolean.
Throws:
RepositoryException - If an error occurs.

 

 

3 replies

M
Manju73Author
Level 2
March 4, 2024

Sorry i forgot to add EventHandler.class in the above snippet .its there in my actual code.

    Imran Khan
    Community Advisor
    Imran KhanCommunity Advisor
    Community Advisor
    March 4, 2024

    @manju73 Since we are looking for property change/add event on a Resource, we can make use of specific Listener named "ResourceChangeListener" - https://sling.apache.org/apidocs/sling9/org/apache/sling/api/resource/observation/ResourceChangeList...

    Sample snippet : (tried and works in my local - AEM 6.5.0)

    Have used the PATHS as is without pattern. Glob pattern is allowed, check the description and use per your need - https://sling.apache.org/apidocs/sling9/org/apache/sling/api/resource/observation/ResourceChangeList...

    package com.aem.demoproject.core.listeners; import org.apache.sling.api.resource.observation.ResourceChange; import org.apache.sling.api.resource.observation.ResourceChangeListener; import org.osgi.service.component.annotations.Component; import org.slf4j.Logger; import org.slf4j.LoggerFactory; import java.util.List; @Component(service = ResourceChangeListener.class, immediate = true, property = { ResourceChangeListener.PATHS + "=/content/trainingproject/en_us/*", ResourceChangeListener.CHANGES + "=CHANGED", ResourceChangeListener.CHANGES + "=ADDED", ResourceChangeListener.PROPERTY_NAMES_HINT + "=jcr:lastModified" }) public class SampleResourceChangeListener implements ResourceChangeListener { private final Logger LOG = LoggerFactory.getLogger(this.getClass()); @Override public void onChange(List<ResourceChange> list) { LOG.info("On add/change of jcr:lastModified"); } }

     

    Reference: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/multiple-paths-handling-in-eventhandler-not-working/td-p/426608

      M
      Manju73Author
      Level 2
      March 4, 2024

      This will work .But i want to  listen pageevent and then we are making changes to jcr:content for that Page .this resource listener will listen if we make any changes in the page so we can't listen page creation events with this one

        M
        Mahesh_Gunaje
        Level 7
        March 5, 2024

        Hi @manju73 

         

        Will this help in your case?

        @Component(service = EventHandler.class, immediate = true, property = { EventConstants.EVENT_FILTER + "=(|(paths=/content/abc/mobile/*)(paths=/content/xyz/desktop/*))", EventConstants.EVENT_TOPIC + "=" + ReplicationAction.EVENT_TOPIC, }) public class CustomReplicationEventHandler implements EventHandler { public void handleEvent(final Event event) {..} }

         

          kautuk_sahni
          Community Manager
          kautuk_sahniCommunity Manager
          Community Manager
          March 7, 2024

          @manju73 Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.

          Kautuk Sahni
          Terms & ConditionsAccessibility statement

          Loading footer...