Article summary

Summary

Discusses how to develop an AEM HTML Template Language (HTL - formerly known as Sightly) component that renders a repeating data set, including digital assets. Use of Sling Models is shown in this article. 

A special thank you to Ratna Kumar Kotla, a top AEM community member, for testing this article to ensure it works.

Digital Marketing Solution(s) Adobe Experience Manager 6.4
Audience Developer
Required Skills Java, HTML, CSS
Version 6.4

Download

Note:

You can download an AEM package that contains the code used in this article. Download the package and deploy using package manager. The purpose of this code is to show the community these concepts in action. That is, it's to illustrate how to write a HTL component that displays a repeating data set using a Sling Model. This community code is for teaching purposes only and not meant to go into production as is.

You can view the application by using the following URL:

http://localhost:4502/editor.html/content/mfHTL64/en.html (assuming you deploy on author).

Introduction

You can create an Adobe Experience Manager 6.4 HTL component that displays repeating information that can be set by an AEM author during design time. For example, consider a typical on-line section of a sports site. 

news11
An example of a web site that shows a repeating data set

Using Experience Manager, you can create a similiar component using HTL and Sling Models. Each section of the HTL component can include:

  • a digital asset (located in the Experience Manager DAM)
  • a heading
  • text

The following illustration shows an Experience Manager HTL component listing various sport stories about a youth football club.

client
An AEM HTL Component that displays a repeating data set

As shown in the previous illustration, the HTL component displays a repeating data set that is set by an AEM author using a Touch UI dialog that contains a granite/ui/components/coral/foundation/form/multifield.

dialog
An HTL component dialog

The multi-field in this article has the following fields based on Granite/Coral data types:

This development article steps you through how to build an AEM 6.4 HTL component by using an AEM Maven Archetype 13 project and a Sling Model.

A Coral/Granite multi-field is based on granite/ui/components/coral/foundation/form/multifield. There are several advantages to working with Coral/Granite multi-field. For one thing, you do not need to write a JS script or use the ACS-Commons package as is typically required when using a granite/ui/components/foundation/form/multifield.

However, there are also some differences too. One important difference to understand is how the data is stored in the JCR. By default, Coral/Granite multi-field data is stored as child nodes, as shown in the illustration. Notice that each multi-field is a separate node, as shown here.

 

nodes
Data is stored as child nodes

Note:

To see the multi-field data stored in the JCR in this example - see /content/mfHTL64/en/jcr:content/root/responsivegrid/touchmulti/products.

Setup Maven in your development environment

You can use Maven to build an OSGi bundle that contains a Sling Servlet. Maven manages required JAR files that a Java project needs in its class path. Instead of searching the Internet trying to find and download third-party JAR files to include in your project’s class path, Maven manages these dependencies for you.

You can download Maven 3 from the following URL:

http://maven.apache.org/download.html

After you download and extract Maven, create an environment variable named M3_HOME. Assign the Maven install location to this environment variable. For example:

C:\Programs\Apache\apache-maven-3.0.4

Set up a system environment variable to reference Maven. To test whether you properly setup Maven, enter the following Maven command into a command prompt:

%M3_HOME%\bin\mvn -version

This command provides Maven and Java install details and resembles the following message:

Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"

Note:

It is recommended that you use Maven 3.0.3 or greater. For more information about setting up Maven and the Home variable, see: Maven in 5 Minutes.

Next, copy the Maven configuration file named settings.xml from [install location]\apache-maven-3.0.4\conf\ to your user profile. For example, C:\Users\scottm\.m2\.

You have to configure your settings.xml file to use Adobe’s public repository. For information, see Adobe Public Maven Repository at http://repo.adobe.com/.

The following XML code represents a settings.xml file that you can use.

<?xml version="1.0" encoding="UTF-8"?>
  
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements.  See the NOTICE file
distributed with this work for additional information
regarding copyright ownership.  The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License.  You may obtain a copy of the License at
  
    http://www.apache.org/licenses/LICENSE-2.0
  
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied.  See the License for the
specific language governing permissions and limitations
under the License.
-->
  
<!--
 | This is the configuration file for Maven. It can be specified at two levels:
 |
 |  1. User Level. This settings.xml file provides configuration for a single user, 
 |                 and is normally provided in ${user.home}/.m2/settings.xml.
 |
 |                 NOTE: This location can be overridden with the CLI option:
 |
 |                 -s /path/to/user/settings.xml
 |
 |  2. Global Level. This settings.xml file provides configuration for all Maven
 |                 users on a machine (assuming they're all using the same Maven
 |                 installation). It's normally provided in 
 |                 ${maven.home}/conf/settings.xml.
 |
 |                 NOTE: This location can be overridden with the CLI option:
 |
 |                 -gs /path/to/global/settings.xml
 |
 | The sections in this sample file are intended to give you a running start at
 | getting the most out of your Maven installation. Where appropriate, the default
 | values (values used when the setting is not specified) are provided.
 |
 |-->
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
  <!-- localRepository
   | The path to the local repository maven will use to store artifacts.
   |
   | Default: ~/.m2/repository
  <localRepository>/path/to/local/repo</localRepository>
  -->
  
  <!-- interactiveMode
   | This will determine whether maven prompts you when it needs input. If set to false,
   | maven will use a sensible default value, perhaps based on some other setting, for
   | the parameter in question.
   |
   | Default: true
  <interactiveMode>true</interactiveMode>
  -->
  
  <!-- offline
   | Determines whether maven should attempt to connect to the network when executing a build.
   | This will have an effect on artifact downloads, artifact deployment, and others.
   |
   | Default: false
  <offline>false</offline>
  -->
  
  <!-- pluginGroups
   | This is a list of additional group identifiers that will be searched when resolving plugins by their prefix, i.e.
   | when invoking a command line like "mvn prefix:goal". Maven will automatically add the group identifiers
   | "org.apache.maven.plugins" and "org.codehaus.mojo" if these are not already contained in the list.
   |-->
  <pluginGroups>
    <!-- pluginGroup
     | Specifies a further group identifier to use for plugin lookup.
    <pluginGroup>com.your.plugins</pluginGroup>
    -->
  </pluginGroups>
  
  <!-- proxies
   | This is a list of proxies which can be used on this machine to connect to the network.
   | Unless otherwise specified (by system property or command-line switch), the first proxy
   | specification in this list marked as active will be used.
   |-->
  <proxies>
    <!-- proxy
     | Specification for one proxy, to be used in connecting to the network.
     |
    <proxy>
      <id>optional</id>
      <active>true</active>
      <protocol>http</protocol>
      <username>proxyuser</username>
      <password>proxypass</password>
      <host>proxy.host.net</host>
      <port>80</port>
      <nonProxyHosts>local.net|some.host.com</nonProxyHosts>
    </proxy>
    -->
  </proxies>
  
  <!-- servers
   | This is a list of authentication profiles, keyed by the server-id used within the system.
   | Authentication profiles can be used whenever maven must make a connection to a remote server.
   |-->
  <servers>
    <!-- server
     | Specifies the authentication information to use when connecting to a particular server, identified by
     | a unique name within the system (referred to by the 'id' attribute below).
     | 
     | NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are 
     |       used together.
     |
    <server>
      <id>deploymentRepo</id>
      <username>repouser</username>
      <password>repopwd</password>
    </server>
    -->
      
    <!-- Another sample, using keys to authenticate.
    <server>
      <id>siteServer</id>
      <privateKey>/path/to/private/key</privateKey>
      <passphrase>optional; leave empty if not used.</passphrase>
    </server>
    -->
  </servers>
  
  <!-- mirrors
   | This is a list of mirrors to be used in downloading artifacts from remote repositories.
   | 
   | It works like this: a POM may declare a repository to use in resolving certain artifacts.
   | However, this repository may have problems with heavy traffic at times, so people have mirrored
   | it to several places.
   |
   | That repository definition will have a unique id, so we can create a mirror reference for that
   | repository, to be used as an alternate download site. The mirror site will be the preferred 
   | server for that repository.
   |-->
  <mirrors>
    <!-- mirror
     | Specifies a repository mirror site to use instead of a given repository. The repository that
     | this mirror serves has an ID that matches the mirrorOf element of this mirror. IDs are used
     | for inheritance and direct lookup purposes, and must be unique across the set of mirrors.
     |
    <mirror>
      <id>mirrorId</id>
      <mirrorOf>repositoryId</mirrorOf>
      <name>Human Readable Name for this Mirror.</name>
      <url>http://my.repository.com/repo/path</url>
    </mirror>
     -->
  </mirrors>
    
  <!-- profiles
   | This is a list of profiles which can be activated in a variety of ways, and which can modify
   | the build process. Profiles provided in the settings.xml are intended to provide local machine-
   | specific paths and repository locations which allow the build to work in the local environment.
   |
   | For example, if you have an integration testing plugin - like cactus - that needs to know where
   | your Tomcat instance is installed, you can provide a variable here such that the variable is 
   | dereferenced during the build process to configure the cactus plugin.
   |
   | As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles
   | section of this document (settings.xml) - will be discussed later. Another way essentially
   | relies on the detection of a system property, either matching a particular value for the property,
   | or merely testing its existence. Profiles can also be activated by JDK version prefix, where a 
   | value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'.
   | Finally, the list of active profiles can be specified directly from the command line.
   |
   | NOTE: For profiles defined in the settings.xml, you are restricted to specifying only artifact
   |       repositories, plugin repositories, and free-form properties to be used as configuration
   |       variables for plugins in the POM.
   |
   |-->
  <profiles>
    <!-- profile
     | Specifies a set of introductions to the build process, to be activated using one or more of the
     | mechanisms described above. For inheritance purposes, and to activate profiles via <activatedProfiles/>
     | or the command line, profiles have to have an ID that is unique.
     |
     | An encouraged best practice for profile identification is to use a consistent naming convention
     | for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc.
     | This will make it more intuitive to understand what the set of introduced profiles is attempting
     | to accomplish, particularly when you only have a list of profile id's for debug.
     |
     | This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo.
    <profile>
      <id>jdk-1.4</id>
  
      <activation>
        <jdk>1.4</jdk>
      </activation>
  
      <repositories>
        <repository>
          <id>jdk14</id>
          <name>Repository for JDK 1.4 builds</name>
          <url>http://www.myhost.com/maven/jdk14</url>
          <layout>default</layout>
          <snapshotPolicy>always</snapshotPolicy>
        </repository>
      </repositories>
    </profile>
    -->
  
    <!--
     | Here is another profile, activated by the system property 'target-env' with a value of 'dev',
     | which provides a specific path to the Tomcat instance. To use this, your plugin configuration
     | might hypothetically look like:
     |
     | ...
     | <plugin>
     |   <groupId>org.myco.myplugins</groupId>
     |   <artifactId>myplugin</artifactId>
     |   
     |   <configuration>
     |     <tomcatLocation>${tomcatPath}</tomcatLocation>
     |   </configuration>
     | </plugin>
     | ...
     |
     | NOTE: If you just wanted to inject this configuration whenever someone set 'target-env' to
     |       anything, you could just leave off the <value/> inside the activation-property.
     |
    <profile>
      <id>env-dev</id>
  
      <activation>
        <property>
          <name>target-env</name>
          <value>dev</value>
        </property>
      </activation>
  
      <properties>
        <tomcatPath>/path/to/tomcat/instance</tomcatPath>
      </properties>
    </profile>
    -->
    
  
<profile>
  
                <id>adobe-public</id>
  
                <activation>
  
                    <activeByDefault>true</activeByDefault>
  
                </activation>
  
                <repositories>
  
                  <repository>
  
                    <id>adobe</id>
  
                    <name>Nexus Proxy Repository</name>
  
                    <url>http://repo.adobe.com/nexus/content/groups/public/</url>
  
                    <layout>default</layout>
  
                  </repository>
  
                </repositories>
  
                <pluginRepositories>
  
                  <pluginRepository>
  
                    <id>adobe</id>
  
                    <name>Nexus Proxy Repository</name>
  
                    <url>http://repo.adobe.com/nexus/content/groups/public/</url>
  
                    <layout>default</layout>
  
                  </pluginRepository>
  
                </pluginRepositories>
  
            </profile>
  
</profiles>
  
  <!-- activeProfiles
   | List of profiles that are active for all builds.
   |
  <activeProfiles>
    <activeProfile>alwaysActiveProfile</activeProfile>
    <activeProfile>anotherAlwaysActiveProfile</activeProfile>
  </activeProfiles>
  -->
</settings>

Note:

The Adobe repository URL is now made secured. Change http://repo.adobe.com/nexus/content/groups/public/ to https://repo.adobe.com/nexus/content/groups/public/.

Create an AEM Maven 13 archetype project

You can create an archetype project by using the Maven archetype plugin. In this example, assume that the working directory is C:\AdobeCQ.

maven
Maven Archetype 11 generated files

To create an Experience Manager archetype project, perform these steps:

1. Open the command prompt and go to your working directory (for example, C:\AdobeCQ).

2. Run the following Maven command:

mvn org.apache.maven.plugins:maven-archetype-plugin:2.4:generate -DarchetypeGroupId=com.adobe.granite.archetypes -DarchetypeArtifactId=aem-project-archetype -DarchetypeVersion=13 -DarchetypeCatalog=https://repo.adobe.com/nexus/content/groups/public/

3. When prompted, specify the following information:

  • groupId - mfHTL64
  • artifactId - mfHTL64
  • version - 1.0-SNAPSHOT
  • package - aem.community.mf
  • appsFolderName - mfHTL64
  • artifactName - mfHTL64
  • componentGroupName - mfHTL64
  • contentFolderName - mfHTL64
  • cssId - mfHTL64
  • packageGroup - mfHTL64
  • siteName - mfHTL64

4. WHen prompted, specify Y.

5. Once done, you will see a message like:

[INFO] BUILD SUCCESS
[INFO] ----------------------------------------------------------------------
[INFO] Total time: 01:42 min
[INFO] Finished at: 2016-04-25T14:34:19-04:00
[INFO] Final Memory: 16M/463M
[INFO] ----------------------------------------------------------------------

6. Change the working directory to mfHTL64 and then enter the following command.

mvn eclipse:eclipse

After you run this command, you can import the project into Eclipse as discussed in the next section.

Add Java files to the Maven project using Eclipse

To make it easier to work with the Maven generated project, import it into the Eclipse development environment, as shown in the following illustration.

project
An Eclipse project

The Eclipse project that you work in to build the OSGi bundle that uses HTL API is mfHTL64.core. You do not have to work in the other projects under mfHTL64.

Note:

Do not worry about the errors reported in Eclipse. It does not read the POM file where the APIs are resolved. You build the bundle with Maven. Eclipse is used to edit the Java files and the POM file.

The next step is to add Java files to the com.htl.community.coral.core.models package named Multifield. This class uses the @Model annontation. It injects a Resource based on the node in the component dialog that corresponds to the granite/ui/components/coral/foundation/form/multifield sling type. 

The following Java code represents the Multifield class. As you can see, it contains very little code other than injecting the Products resource (this corresponds to cq:dialog/content/items/column/items/products in the dialog).

The HTL code in the component binds to this resource and contains iteration logic that displays the values in the multi-field (this is shown later in this article). 

package aem.community.mf.core.models;


import javax.annotation.PostConstruct;
import javax.inject.Inject;
import javax.inject.Named;

import org.apache.sling.api.resource.Resource;
import org.apache.sling.models.annotations.Default;
import org.apache.sling.models.annotations.Model;
import org.apache.sling.models.annotations.Optional; 
import org.apache.sling.settings.SlingSettingsService;

@Model(adaptables = Resource.class)
public class Multifield {

	// Inject the products node under the current node
	@Inject
	@Optional
	public Resource products;

	// No need of a post construct as we don't have anything to modify after the
	// model is constructed
}

Modify the Maven POM file

Add the following POM dependencies to the POM file located at C:\AdobeCQ\mfHTL64.

<dependency>
    <groupId>com.adobe.aem</groupId>
    <artifactId>uber-jar</artifactId>
    <version>6.4.0</version>
    <classifier>apis</classifier>
    <scope>provided</scope>
</dependency>
               
  <dependency>
       <groupId>org.apache.geronimo.specs</groupId>
       <artifactId>geronimo-atinject_1.0_spec</artifactId>
       <version>1.0</version>
       <scope>provided</scope>
   </dependency>

You need to modify two POM files. The first one is the parent POM file shown in this illustration.

maven
Parent POM

Add the dependency shown above to the Parent POM file. Next, modify the POM file located at C:\AdobeCQ\mfHTL64\core. The following code represents this POM file.

<?xml version="1.0" encoding="UTF-8"?>
<!--
 |  Copyright 2017 Adobe Systems Incorporated
 |
 |  Licensed under the Apache License, Version 2.0 (the "License");
 |  you may not use this file except in compliance with the License.
 |  You may obtain a copy of the License at
 |
 |      http://www.apache.org/licenses/LICENSE-2.0
 |
 |  Unless required by applicable law or agreed to in writing, software
 |  distributed under the License is distributed on an "AS IS" BASIS,
 |  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 |  See the License for the specific language governing permissions and
 |  limitations under the License.
-->
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>
    <parent>
        <groupId>mfHTL64</groupId>
        <artifactId>mfHTL64</artifactId>
        <version>1.0-SNAPSHOT</version>
        <relativePath>../pom.xml</relativePath>
    </parent>
    <artifactId>mfHTL64.core</artifactId>
    <packaging>bundle</packaging>
    <name>mfHTL64 - Core</name>
    <description>Core bundle for mfHTL64</description>
    <build>
        <plugins>
            <plugin>
                <groupId>org.apache.sling</groupId>
                <artifactId>maven-sling-plugin</artifactId>
            </plugin>
            <plugin>
                <groupId>org.apache.felix</groupId>
                <artifactId>maven-bundle-plugin</artifactId>
                <extensions>true</extensions>
                <configuration>
                    <instructions>
                        <!-- Import any version of javax.inject, to allow running on multiple versions of AEM -->
                        <Import-Package>javax.inject;version=0.0.0,*</Import-Package>
                        <Sling-Model-Packages>
                            aem.community.mf.core
                        </Sling-Model-Packages>
                    </instructions>
                </configuration>
            </plugin>
        </plugins>
    </build>

    <dependencies>
        <!-- OSGi Dependencies -->
        <dependency>
            <groupId>com.adobe.aem</groupId>
            <artifactId>uber-jar</artifactId>
            <classifier>apis</classifier>
        </dependency>
     
        <dependency>
            <groupId>org.apache.geronimo.specs</groupId>
            <artifactId>geronimo-atinject_1.0_spec</artifactId>
        </dependency>
        <dependency>
            <groupId>org.osgi</groupId>
            <artifactId>osgi.core</artifactId>
        </dependency>
        <dependency>
            <groupId>org.osgi</groupId>
            <artifactId>osgi.cmpn</artifactId>
        </dependency>
        <dependency>
            <groupId>org.osgi</groupId>
            <artifactId>osgi.annotation</artifactId>
        </dependency>
        <!-- Other Dependencies -->
        <dependency>
            <groupId>org.slf4j</groupId>
            <artifactId>slf4j-api</artifactId>
        </dependency>
        <dependency>
            <groupId>javax.jcr</groupId>
            <artifactId>jcr</artifactId>
        </dependency>
        <dependency>
            <groupId>javax.servlet</groupId>
            <artifactId>servlet-api</artifactId>
        </dependency>
        <dependency>
            <groupId>com.adobe.aem</groupId>
            <artifactId>uber-jar</artifactId>
            <classifier>apis</classifier>
        </dependency>
        <dependency>
            <groupId>org.apache.sling</groupId>
            <artifactId>org.apache.sling.models.api</artifactId>
        </dependency>
        <dependency>
            <groupId>junit</groupId>
            <artifactId>junit</artifactId>
        </dependency>
        <dependency>
            <groupId>org.mockito</groupId>
            <artifactId>mockito-core</artifactId>
        </dependency>
        <dependency>
            <groupId>junit-addons</groupId>
            <artifactId>junit-addons</artifactId>
        </dependency>
    </dependencies>
</project>

Build the OSGi bundle using Maven

To build the OSGi bundle by using Maven, perform these steps:

  1. Open the command prompt and go to the C:\AdobeCQ\mfHTL64.
  2. Run the following maven command: mvn -PautoInstallPackage install.
  3. The OSGi component can be found in the following folder: C:\AdobeCQ\mfHTL64\core\target. The file name of the OSGi component is mfHTL64.core-1.0-SNAPSHOT.jar.

The command -PautoInstallPackage automatically deploys the OSGi bundle to AEM.

Create the HTL Front End Component

Perform these tasks using CRXDE Lite:

1. Right click on /apps/mfHTL64/components/content and then select New, Component.

2. Enter the following information into the Create Component dialog box:

  • Label: The name of the component to create. Enter touchmulti.
  • Title: The title that is assigned to the component. Enter touchmulti.
  • Description: The description that is assigned to the template. Enter touchmulti.
  • Super Resource Type: Enter foundation/components/parbase.
  • Group: The group in the side rail or side kick where the component appears. Enter mfHTL64. (The component is located under the General heading in the Touch UI side rail.)

3. Click Ok.

Once done, you will see the component as shown in the following illustration.

CRXDE
An HTL component

Note:

Rename touchmulti.jsp to touchmulti.html.

Add a dialog to the HTL component

A dialog lets an author click on the component in the Touch UI (or Classic UI) view during design time and enter values that are used by the component. The component created in this development article lets the AEM author enter information in a multi-field control.

dialog
Dialog for the HTL component

The following illustration shows the JCR nodes for this component. The multifield node is products and the second redbox represents the fields that appear in the multifield. 

MF
JCR nodes that creates the component dialog

To create a dialog by using CRXDE lite, perform these tasks:

1. Select /apps/mfHTL64/components/content/touchmulti.

2. Right click and select Create, Create Node.

3. Enter the following values:

  • Name: cq:dialog
  • Type: nt:unstructured

4. Add the following property to the cq:dialog node.

  • sling:resourceType (String) - cq/gui/components/authoring/dialog

5. Select /apps/mfHTL64/components/content/TabComponent/cq:dialog.

6. Right click and select Create, Create Node. Enter the following values:

  • Name: content
  • Type: nt:unstructured

7. Add the following property to the content node.

  • sling:resourceType (String) - granite/ui/components/coral/foundation/fixedcolumns

8. Select /apps/mfHTL64/components/content/touchmulti/cq:dialog/content.

9. Right click and select Create, Create Node. Enter the following values:

  • Name: items
  • Type: nt:unstructured

10. Select /apps/mfHTL64/components/content/touchmulti/cq:dialog/content/items.

11. Right click and select Create, Create Node. Enter the following values:

  • Name: column
  • Type: nt:unstructured

12. Add the following property to the column node.

  • sling:resourceType (String) - granite/ui/components/coral/foundation/container

13. Select /apps/mfHTL64/components/content/touchmulti/cq:dialog/content/items/column.

14. Right click and select Create, Create Node. Enter the following values:

  • Name: items
  • Type: nt:unstructured

15. Select /apps/mfHTL64/components/content/touchmulti/cq:dialog/content/items/column/items.

16. Right click and select Create, Create Node. Enter the following values:

  • Name: products
  • Type: nt:unstructured

17. Add the following property to the products node (notice this is the multifield node).

  • sling:resourceType (String) - granite/ui/components/coral/foundation/form/multifield
  • composite (Boolean) - true
  • eaem-show-on-collapse (String) - EAEM.showProductName
  • fieldLabel (String) - Products

18. Select /apps/mfHTL64/components/content/touchmulti/cq:dialog/content/items/column/items/products.

19. Right click and select Create, Create Node. Enter the following values:

  • Name: field
  • Type: nt:unstructured

20. Add the following property to the field node.

  • sling:resourceType (String) - granite/ui/components/coral/foundation/container
  • name (String) - ./products

21. Select /apps/mfHTL64/components/content/touchmulti/cq:dialog/content/items/column/items/products/field.

22. Right click and select Create, Create Node. Enter the following values:

  • Name: items
  • Type: nt:unstructured

23. Select /apps/mfHTL64/components/content/touchmulti/cq:dialog/content/items/column/items/products/field/items.

24. Right click and select Create, Create Node. Enter the following values:

  • Name: column
  • Type: nt:unstructured

25. Add the following property to the field node.

  • sling:resourceType (String) - granite/ui/components/coral/foundation/container

26. Select /apps/mfHTL64/components/content/touchmulti/cq:dialog/content/items/column/items/products/field/items/column.

27. Right click and select Create, Create Node. Enter the following values:

  • Name: items
    Type: nt:unstructured

28. Select /apps/mfHTL64/components/content/touchmulti/cq:dialog/content/items/column/items/products/field/items/column/items.

29. Right click and select Create, Create Node. Enter the following values:

  • Name: product
  • Type: nt:unstructured

30. Add the following property to the field node.

  • sling:resourceType (String) - granite/ui/components/coral/foundation/form/textfield
  • fieldDescription (String) - Name of Product
  • fieldLabel (String) - Product Name
  • name (String) - ./product

31. Select /apps/mfHTL64/components/content/touchmulti/cq:dialog/content/items/column/items/products/field/items/column/items.

32. Right click and select Create, Create Node. Enter the following values:

  • Name: path
  • Type: nt:unstructured

33. Add the following property to the field node.

  • sling:resourceType (String) - granite/ui/components/coral/foundation/form/pathfield
  • fieldDescription (String) - Select Path
  • fieldLabel (String) - Path
  • name (String) - ./pathbr 
  • rootPath (String) - /content/dam/sports (this location is created by the package shown at the beginning of this article)

34. Select /apps/mfHTL64/components/content/touchmulti/cq:dialog/content/items/column/items/products/field/items/column/items.

35. Right click and select Create, Create Node. Enter the following values:

  • Name: type
  • Type: nt:unstructured

36. Add the following property to the field node.

  • sling:resourceType (String) - granite/ui/components/coral/foundation/form/textarea
  • fieldLabel (String) - Description
  • fieldDescription (String) - Description
  • name (String) - ./desc 

Note:

If you install the package at the start of this article, then you do not need to build the JCR nodes that represent the dialog.

Add HTL code

Add code to the HTML file named touchmulti.html located in the following JCR location:

/apps/mfHTL64/components/content/touchmulti/touchmulti.html

In the HTL file, notice this line of code:

<data-sly-use.multiItems="aem.community.mf.core.models.Multifield>

This is how you create an instance of the Multifield object which contains an inject Product resource (which represents the Sling Model).

Add the following code.

<style>
 
 
h2 {
    display: inline;
}
img{
    float:left;
}
 
 
</style>


<h2>Current Issue</h2>
<div
    data-sly-use.multiItems="aem.community.mf.core.models.Multifield">
    <div data-sly-list.head="${multiItems.products.listChildren}">


		<div style="height:250px;"><img src=${head.pathbr} height=200 width=270 style="padding:4px"/><h2>${head.product}</h2>
                             <p>${head.desc}</p>

                             </div>
                             <hr>

   </div>
</div>

Here, data-sly-list.head maps to all of the items in the multifield using ${multiItems.products.listChildren}.

That is, for each node under:

/content/mfHTL64/en/jcr:content/par/touchmulti/products

an iteration occurs and the value of desc (the text area), pathbr (the field browser), and product (the text field) is written out. (There is a separate node for each multifield that an author fills out). 

View the output of the HTL component

To access the component (assuming you installed the package shown at the start of this article), enter the following URL: 

http://localhost:4502/editor.html/content/mfHTL64/en.html

The following video shows the HTL component.

A Sling Model HTL component

A Sling Model HTL component
A Sling Model HTL component

Note:

If you have not installed the package, you need to drag and drop the touchmulti onto the page and set the dialog. To see this result, install the package at the start of the article, or set your own dialog with different values and images from the AEM DAM. 

See also

Join the AEM community at: Adobe Experience Manager Community

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy