Ir al contenido principal

How to configure the Sling Model for the AEM Angularjs component

In the previous video we saw How to create an AEM SPA component using Angularjs, but we found one problem, whenever we made a change we had to refresh the page to see the changes. In this second part I will show how to configure the sling model to expose the component's properties to fix the issue, above is the vid and below you will find some useful notes.
  1. 1.

    Pre-reqs

  2. 2.

    Exposing the model

    • Go to your IDE or editor and look for the model inside the core module, the model name is BasicModel and should be located inside the models package
    • First, let’s set the model’s adaptables to SlingHttpServletRequest and import the class
      import org.apache.sling.api.SlingHttpServletRequest;
      @Model(adaptables = SlingHttpServletRequest.class)
      
    • Then we need to import and implement the ComponentExporter interface and also define the getExportedType method to return the name for the resource type associated with the basic component
      import com.adobe.cq.export.json.ComponentExporter;
      ...
      public class BasicModel implements ComponentExporter {
          protected static final String BASIC_COMPONENT_RESOURCETYPE = "angularjs-simple-example/components/basic-component";
          ...
      
          public String getExportedType() {
              return BASIC_COMPONENT_RESOURCETYPE;
          }
      
          ...
      }
      
    • Finally import ExporterConstants and the Exporter annotation, add the ComponentExporter as an adapter and define the resourceType. For the exporter set the name as SLING_MODEL_EXPORTER_NAME and the extension as SLING_MODEL_EXTENSION.
      import org.apache.sling.models.annotations.Exporter;
      import com.adobe.cq.export.json.ExporterConstants;
      
      @Model(adaptables = SlingHttpServletRequest.class,
              adapters = {ComponentExporter.class},
              resourceType = BASIC_COMPONENT_RESOURCETYPE)
      @Exporter(name = ExporterConstants.SLING_MODEL_EXPORTER_NAME, extensions = ExporterConstants.SLING_MODEL_EXTENSION)
      
    • Let’s build and deploy the app again
      mvn clean install -PautoInstallPackage -Padobe-public
      
    • Go now to the page edit the component make some changes and click save, the changes get reflected right away
  3. 3.

Comentarios

Entradas populares de este blog

Create a custom AEM workflow process step with a dialog

In this tutorial I talk about how to create a custom workflow step process with an additional dialog for configuring it, above is the vid and below you will find some useful notes. 1. Pre-reqs Have access to an Adobe Experience Manager instance. Have Maven installed, understand how it works and also understand how to use Adobe's archetype, you can watch my video about maven here: Creating an AEM application using Maven and Adobe's archetype 2. What is an AEM Workflow and workflow model Workflows allow you to automate different tasks inside AEM by defining a s

How to create an AEM component using Reactjs

In this tutorial, I will show how to use use Adobe's archetype to create an AEM application with React.js support and also how to add a new React.js component so that it can be added into a page, above is the vid and below you will find some useful notes. In the second part we will see how to configure the Sling Model for the AEM React component. 1. Pre-reqs Have access to an Adobe Experience Manager instance. You will need aem 6.4 Service Pack 2 or newer. Have Maven installed, understand how it works and also understand how to use Adobe's archetype, you can watch my video about maven here: Creating an AEM application using Maven and Adobe's archetype 2.

Creating Docker containers for Adobe Experience Manager

This is a Docker tutorial for creating a docker image for the Galen framework, above is the vid and below you will find some of the steps followed. Adobe experience manager is a content management system which in a nutshell is an application that allows us to create web sites to be consumed by end users. You might be familiar with other such applications like wordpress or drupal which serves the same purpose A typical deployment would be comprised of two AEM instances, the author instance used for creating and modifying content, the publish instance which serves the content and finally we have a dispatcher which is a static web server used for caching, load balancing and some security purposes. We can configure an AEM instance to work as an author or publish instance by either changing the file name