AEM is known for its re-usability and inheritance. It’s astonishing how a single component can be easily re-used across multiple locations.

Adobe provides a set of pre-defined components that comes with all the functionalities to build a website called core components.

To extend those components, a mechanism called proxying is used – where the instance of the component would be referred in our project. Let’s dive deep into the process.

Pre-requisite:

Installation of core components into the AEM server.

Process:

To proxy, the core component in the custom code base, just refer to the core component’s path as sling:resourceSuperType like below

<?xml version="1.0" encoding="UTF-8"?>
<jcr:root xmlns:sling="http://sling.apache.org/jcr/sling/1.0" xmlns:cq="http://www.day.com/jcr/cq/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0"
    jcr:primaryType="cq:Component"
    jcr:title="Button"
    sling:resourceSuperType="core/wcm/components/button/v1/button"
    componentGroup="allAEMByKiranVedantam - Content"/>

The component structure looks like this

Note: While creating a new project using the latest adobe archetype, most of the core component’s proxies will be automatically created.

Please like & share the content if you find it useful. Let me know if you want me to add any topics to the blog from AEM. Do not forget to clap for me.

Leave a comment

Design a site like this with WordPress.com
Get started