Friday, 14 August 2015

Creating an AEM Sling Post Processor

You can develop a custom Sling Post Processer for Adobe Experience Manager (AEM) that is invoked after a Sling Post Servlet operation occurs. For example, assume that an AEM page posts data to AEM by using a Sling Post Servlet operation. That is, once the Sling Post Servlet operation makes changes to the AEM JCR, but before the changes are persistet, the custom Sling Post Processer is invoked. Using a Sling Post Processer, you can perform tasks such as creating a log of JCR node changes. A Sling Post Processer is as an OSGi bundle that implements SlingPostProcessor.

The article walks you through how to create a Sling Post Processer that is invoked when an AEM mobile form submits data to AEM by using a Sling Post Servlet operation.



Adobe Digital Marketing Community

Join the Adobe Digital Marketing Community. Start by clicking this banner



I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with over 18 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.

TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeMktgCare.

1 comment:

  1. Hi,
    your blog is more informative. Can you please suggest me some sources to download the DAM Assets metadata out of AEM JCR?

    ReplyDelete