Ir al contenido principal

How to organize your clientlibs JavaScript files by Integrating Adobe Experience Manager and System.Js


Some simple steps to organize your clientlibs javascript files using System.js

Repository with the final code

Pre-requisites

  • An Adobe Experience Manager (AEM) Instance
  • Java  
  • Maven
  • SystemJs

Creating the app

  • AEM project archetype
  • Creating your first Adobe Experience Manager 6.2 Project using Adobe Maven Archetype 10
  • Assuming you that have maven in the path, if not change "mvn" to for example "c:\program files\maven3.3.9\bin\mvn"
    
    mvn archetype:generate -DarchetypeGroupId=com.adobe.granite.archetypes -DarchetypeArtifactId=aem-project-archetype -DarchetypeVersion=10 -DarchetypeRepository=https://repo.adobe.com/nexus/content/groups/public/ -DgroupId=AEM62App -DartifactId=echo62 -Dversion=0.1.0-SNAPSHOT -Dpackage=com.aem.community -DappsFolderName=AEM62App -DartifactName=AEM62App -DcomponentGroupName=AEM62 -DcontentFolderName=AEM62App -DcssId=AEM62CSS -DpackageGroup=AEM62App  -DsiteName=AEM62App
    
  • Add the import-package element with javax.inject;version=0.0.0,* inside the instructions element in the pom.xml:48 file to fix the:
    org.apache.sling.api.scripting.ScriptEvaluationException: org.apache.sling.scripting.sightly.SightlyException: Cannot find a a file corresponding to class com.aem.community.core.models.HelloWorldModel in the repository.
    Processing Info:
    Page             = /content/AEM62App/en 
    Resource Path    = /content/AEM62App/en/jcr:content/par/servicecomponent 
    Cell             = helloworld 
    Cell Search Path = page/par|parsys/helloworld 
    Component Path   = /apps/AEM62App/components/content/helloworld
  • Add dependencies="[jquery]" at the end of the .content.xml clientlib file
  • Add System.js, my-module.js and reusable-module.js alongside the .content.xml.  I suggest you add a folder also to store all your js files and also many more sub-folders inside that one so you have each module in its own "set"
  • Remember to add the files and their respective locations to the js.txt as seen in the video
  • Modify the helloworld.html:22 so we can target it using the new module
  • mvn clean install -PautoInstallPackage for installing the app
  • Et voilà, we now have ourselves a new project using system.js and adobe experience manager (AEM)

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 sequence of steps to be executed and the actions to be performed at each step. A workflow model represents the definition of a workflow using nodes for the steps or actions to be executed and transitions to define how the steps are organized and what is going to be th…

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 for the jar file java -jar cq-author-450…

Creating a Mongo replicaset using docker: Mongo replicaset + Nodejs + Docker Compose

This is a Docker tutorial for creating a Mongo replica set using docker compose and also a couple more containers to experiment with the replica set, above is the vid and below you will find some of the steps followed.
StepsPre-reqsHave node.js installedAnd docker installed (make sure you have docker-compose as well)Create a container for defining configurations for a mongo instanceCreate a container for setting up the replica setCreate a simple node app using expressjs and mongoose (A modified version from the previous video)Create a docker-compose file with the mongo and setup containers and two additional containers for experimenting with the replica setBuild, Run and experiment with your new containers Create a dockerfile for the first mongo container (not really needed but you could configure more stuff if needed)Include container with mongo preinstalled: FROM mongoCreate default/working directory: WORKDIR /usr/src/configsCopy mongo's configurations file into the container
C…