@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
AEM's dropdown comes with a simple and useful feature, to toggle visibility of other Dialog fields based on its selection. An OOTB implementation is available for component "/apps/core/wcm/components/list/v1/list" Let's quickly check how to configure it (verified on AEM 6.3 with Coral-3 dropdown): Step 1: Register dropdown that is supposed to show/hide other dialog fields. Achieved … Continue reading Toggle Field visibility based on dropdown’s value – Coral 3
In template editors, policies are used to configure component design. Example: component's design configurations, allowed components for a container, mapping asset into components etc. Configuring a template-editor's policy is similar to a Static template's design dialog. Following are the steps to define and access a new policy: Step 1: Create policy configuration dialog A component's policy dialog … Continue reading AEM Template Editor – Design configuration via policies
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.
In AEM component dialog, we often implement multifield which comprise of multiple widgets. Here we would cover multifield which would store values in json format using: Coral 3 multifield acs-aem-commons package javax.json.JsonObject API: Since, org.apache.sling.commons.json.JSONObject has been deprecated. STEP 1: Create a component. STEP 2: Create component dialog with multifield comprising of: textfield pathbrowser Add acs-commons-nested="JSON_STORE" … Continue reading AEM – Coral 2 multifield with acs-aem-commons JSON_STORE
There are few modifications to the way Granite UI components are configured for Coral 3 components. Example: radio, checkbox, multifield etc. Sharing snippets for frequently used Granite UI components (verified on AEM 6.3): Alert: Accordian: Checkbox: value: The submit value of the field when it is checked. uncheckedValue: The submit value of the field when it … Continue reading Coral 3 – Granite UI components