There are multiple ways to address this requirement
Technique 1: Sling Events - There is modern compared to ResourceChangeListeners. Here is a full example. You create an EventHandler and subscribe to `distribution.paths` event for "ADD" type. The event will be invoked everytime asset gets published.
@Component(immediate = true, property = { "event.topics=org/apache/sling/distribution/importer/package/imported",
"event.filter=(|(distribution.type=ADD)(distribution.type=DELETE))" })
public class SlingDistributionEventHandler implements EventHandler {
public static final String DISTRIBUTION_PATHS = "distribution.paths";
@Override
public void handleEvent(Event event) {
if (event.getProperty(DISTRIBUTION_PATHS) != null) {
String[] pagePath = (String[]) event.getProperty(DISTRIBUTION_PATHS);
}
}
Technique 2: Workflow Launchers - This is an old technique. Not recommended considering, in cloud environments, launchers gets invoked multiple times. And may result in accidently executing multiple times.
Technique 3: Using App Builder IO - On Cloud world, we are working hard to break AEM monolith into microservices. Adobe provides App Builder to run actions OUTSIDE AEM. So when an asset gets processed, AEM dispatches an Event. You ll build an IO action to subscribe to AEM event and continue your remaining work. Beauty is, this microservice action runs completely OUTSIDE AEM. And runs with Cloud power, scaling up/down. You need not worry about volume, job heaviness, CPU etc, since this is outside AEM.
Highly recommended to explore AppBuilder route and create an action outside AEM. If not feasible, stick to option1, sling events.
