Sling supports filter processing by applying filter chains to the requests before actually dispatching to the servlet or script for processing. They can be used to call a servlet, to redirect to another page, to authenticate request, preprocessing, post-processing of mark up, logging, measuring, decoration or adding/removing request parameters. Filters to be used in such … Continue reading DS Annotations – Sling Filter
The best way to allow communication between two AEM instance is by: Exposing a service from the AEM instance which acts a source of information (say Source-AEM) Consuming the exported service in the required remote AEM (Consumer-AEM). In case, you have a use-case where: A Service cannot be exposed via source AEM A utility … Continue reading Connecting AEM from remote AEM instance (via JCR API)
With AEM 6.2, we can use the new Declarative Service annotations. These are improvements over Felix annotations. Adding the recommendation excerpt from Apache Felix website: While the Apache Felix Maven SCR Plugin is a great tool (see below), for developing OSGi components using Declarative Services you should use the official annotations from the OSGi R6 … Continue reading DS Annotations – dependency updates
@Component Annotation An component is a piece of code that is managed by OSGi container. The container would be responsible for its instantiation and management. Attributes of a component: The above table have been noted from: https://www.knopflerfish.org/releases/5.2.0/docs/javadoc/org/osgi/service/component/annotations/Component.html configurationPolicy: The attribute can hold following values of ConfigurationPolicy IGNORE: Always allow the component configuration to be satisfied and do … Continue reading DS Annotations – Component, property and configurations
Define multiple implementations of a Service, and then execute all/specific implementation depending on the use-case.
OSGi Configuration factory for multiple service configurations with single implementation.
Here is a code snippet that can be used to fetch AEM's product information via APIs. Information printed in logs: