Hi @hptarora In case you are using AEMaaCS you could leverage Cloud Events: https://developer.adobe.com/experience-cloud/experience-manager-apis/guides/events/. I believe one of its use-cases is exactly the one you need. You have a Publish event webhook specially for sites, among others, which you c...

Is this what are you looking for ?  Or you need the under the hood coding and logic stuff that the framework is doing ?

I believe AEM SPA is using Sling Model Exporter to get JSON representation of requested page. As you don't have HTL. You only serve a JSON to your React or Angular components. Sling Model Exporter documentation:https://experienceleague.adobe.com/en/docs/experience-manager-learn/foundation/developmen...

More explanations here : https://www.google.com/url?sa=t&source=web&rct=j&opi=89978449&url=https://medium.com/%40manumathew28.94/understanding-aem-workflow-b017f0519c44&ved=2ahUKEwiPnLqIv_WJAxX0RPEDHcDcIC4QFnoECBMQAQ&usg=AOvVaw3t_nAAurDhHoF56yoa-9k9 Is like you have workflow definition in /conf and ...

Hi. I think this is saying all:https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/developing/extending-aem/extending-workflows/workflows-models  

And a basic such modern Filter implementation would look something like this:import javax.servlet.Filter; import javax.servlet.FilterChain; import javax.servlet.FilterConfig; import javax.servlet.ServletException; import javax.servlet.ServletRequest; import javax.servlet.ServletResponse; import org...

Hi @jayv25585659 Yes it is. You can find the full story here: https://medium.com/globant/declarative-services-from-felix-scr-to-osgi-4770509f1965Long story short, AEM moved from SCR to OSGi annotations, which is exactly the case you raised.

Check if you use optional injection strategy as well in your model : https://sling.apache.org/documentation/bundles/models.html#optional-and-required-1

Hi @ShamliKh  The property in sling Servlet main servlet that you are loiking gor is sling.max.calls. But few consideration to have in mind:This prop wad introduced to avoid endleess loop of calls, to be carefull when you modify it. I would put the lowest possible value that makes your use case work...

What if you don't tamper it, so that yoy avoid unexpected behaviors, and you rather create a new custom list component that extends the core one, and in addition you add a clientlib and manipulate the dom to hide what you don't need ?