“Every custom include of ‘extraClientlibs’ will live on the page until page reload therefore JS functions could easily break logic in other dialogs during the page editing.”

1. Avoid Including Everything in cq.authoring.dialog

The cq.authoring.dialog category should reserve space only for utility methods applicable across all dialogs without causing conflicts.

2. Use Separate, Descriptive Categories

Create distinct categories using package or folder paths to prevent name collisions:

1
categories="[project-a.components.product.wizzard.authoring]"

3. Add Dialog Validation Logic

Implement resource type verification at the beginning of custom JS to ensure code executes only in the intended dialog:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
(function (document, $) {
  "use strict";
  
  const DIALOG_RESOURCE_TYPE = "project-a/components/product/wizzard";
  
  function isTargetDialog($formElement, dlgResourceType) {
    const resourceType = $formElement.find("input[name='./sling:resourceType']").val();
    return resourceType === dlgResourceType;
  }
  
  $(document).on("dialog-ready", function () {
    const $formElement = $(this).find('coral-dialog form.foundation-form');
    if (!isTargetDialog($formElement, DIALOG_RESOURCE_TYPE)) {
      console.debug("Skip the listener, not a ", DIALOG_RESOURCE_TYPE, " dialog.");
      return;
    }
    // Implementation code here
  });
})(document, Granite.$);

These practices promote maintainable, scalable dialog implementations across growing AEM projects.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
java.lang.UnsupportedOperationException: The query read or traversed more than 100000 nodes. 
To avoid affecting other tasks, processing was stopped.
	at org.apache.jackrabbit.oak.query.FilterIterators.checkReadLimit(FilterIterators.java:70)
	at org.apache.jackrabbit.oak.plugins.index.Cursors.checkReadLimit(Cursors.java:67)
	at org.apache.jackrabbit.oak.plugins.index.lucene.LucenePropertyIndex$LucenePathCursor$1.next(LucenePropertyIndex.java:1730)
	at org.apache.jackrabbit.oak.plugins.index.lucene.LucenePropertyIndex$LucenePathCursor$1.next(LucenePropertyIndex.java:1711)
	at com.google.common.collect.Iterators$7.computeNext(Iterators.java:646)
	at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143)
	at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138)
	at org.apache.jackrabbit.oak.plugins.index.Cursors$PathCursor.hasNext(Cursors.java:216)
	at org.apache.jackrabbit.oak.plugins.index.lucene.LucenePropertyIndex$LucenePathCursor.hasNext(LucenePropertyIndex.java:1751)
	at org.apache.jackrabbit.oak.query.ast.SelectorImpl.next(SelectorImpl.java:432)
	at org.apache.jackrabbit.oak.query.QueryImpl$RowIterator.fetchNext(QueryImpl.java:824)
	at org.apache.jackrabbit.oak.query.QueryImpl$RowIterator.hasNext(QueryImpl.java:851)
	at org.apache.jackrabbit.oak.jcr.query.QueryResultImpl$1.fetch(QueryResultImpl.java:98)

Solutions

In this situation, developers can:

• Define an Oak index for the query
• Redesign repository taxonomy or structure for improvement
• Update Oak indexes to cover the query
• Use oak:Unstructured instead of nt:unstructured and sling:Folder instead of sling:OrderedFolder when ordering is not required
• Consider other architectural approaches

Development Workaround

During development, you can temporarily increase LimitReads and LimitInMemory parameters:

1. Navigate to QueryEngineSettings at http://localhost:4502/system/console/jmx/org.apache.jackrabbit.oak%3Aname%3Dsettings%2Ctype%3DQueryEngineSettings
2. Increase the selected parameters

Note: This is for development only; do not deploy to production.

The following steps enable this process:

1. Create a package with digital assets and deploy to AEM package manager
2. Stop the com.day.cq.workflow.launcher.impl.WorkflowLauncherImpl — this prevents getting stuck on rendition workflow
3. Install the package from step 1
4. Start the com.day.cq.workflow.launcher.impl.WorkflowLauncherImpl

These steps allow importing assets on AEM quickly with renditions.

1
http://localhost:4502/system/console/status-productinfo

This endpoint displays the installed AEM product version details for the running instance.

1. Open Project structure (shortcut on Windows: Ctrl + Alt + Shift + S)

2. Find Maven: com.adobe.aem:uber-jar:apis:6.4.4 (or another uber jar which you are using for the project) and click the plus icon with the Earth

3. Put the following as a documentation URL:

1
https://helpx.adobe.com/experience-manager/6-4/sites/developing/using/reference-materials/javadoc/index.html

After completing these actions you’ll be able to see API doc hints (on Windows with Ctrl + Q).

Installation Steps

1. Open Print Server Properties
   • Press Win + R
   • Enter printui /s /t2
   • Click OK
2. Add Printer
   • Click “Add…” in the Printer Server Properties window
   • Follow the subsequent dialog prompts
3. Select Driver
   • In the Windows Update window, select manufacturer: HP
   • Choose driver: HP LaserJet 1020
   • Click “Next” then “Finish”

Upon completing these steps, the HP 1018 printer will be installed on the system.

1
WARNING: Could not open/create prefs root node Software\JavaSoft\Prefs at root 0x80000002. Windows RegCreateKeyEx(…) returned error code 5.

Solution

Create two registry keys:

• HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Prefs
• HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\JavaSoft\Prefs

Steps to Fix

1. Open the Registry Editor (Win + R → type regedit → Enter)
2. Navigate to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node
3. Right-click on WOW6432Node, select New → Key and name it JavaSoft
4. Create a Prefs key within JavaSoft
5. Repeat steps 3–4 for the HKEY_LOCAL_MACHINE\SOFTWARE path

Installed AEM Version:

1
http://localhost:4502/system/console/status-productinfo

AEM Run Mode:

Navigate to:

1
http://localhost:4502/system/console/bundles

Then go to Status → Sling Settings menu.

Place either script at the same directory level as license.properties.

Windows (start.bat)

1
2
3
4
5
6
7
8
del /s /q ".\crx-quickstart\logs\*.*"

set CQ_PORT=4502
set CQ_RUNMODE=author,localdev
set CQ_JVM_OPTS=-Xmx2048m -XX:+UseG1GC -XX:-UseGCOverheadLimit -Duser.language=en -Duser.region=US -Duser.timezone=UTC -Djava.awt.headless=true -Dfile.encoding=UTF-8 -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=8001

cd ./crx-quickstart/bin
call ./start.bat

macOS

1
2
3
4
5
6
7
8
9
10
11
12
13
14
#!/bin/sh

echo "Clean AEM logs"
find crx-quickstart/logs/ -type f -delete

echo "Set AEM parameters"
export CQ_PORT="4502"
export CQ_DEBUG_OPTS="-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=8001"
export CQ_LOCALE_OPTS="-Duser.language=en -Duser.region=US -Duser.timezone=UTC -Dfile.encoding=UTF-8"
export CQ_RUNMODE="author,nosamplecontent"
export CQ_JVM_OPTS="-Djava.awt.headless=true -Xmx2048m -XX:+UseG1GC -XX:-UseGCOverheadLimit $CQ_LOCALE_OPTS $CQ_DEBUG_OPTS"

echo "Start AEM instance"
crx-quickstart/bin/start "$@"

Steps

1. Download JDK from the Oracle website

2. Install 7-zip if not already installed

3. Create an unpack.bat file in the same folder as the downloaded JDK installer, with content depending on the JDK version:

Batch file for JDK 8

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
@echo off
set PATH=%PATH%;C:\Program Files\7-Zip\

rmdir /s /q "%~dp0\jdk-out"
rmdir /s /q "%~dp0\unpacked-jdk"
7z x %1 -o"%~dp0\jdk-out"
cd /d "jdk-out\.rsrc\1033\JAVA_CAB10"
extrac32 111
7z x tools.zip -ojdk
cd /d "jdk"
for /r %%x in (*.pack) do .\bin\unpack200 -r "%%x" "%%~dx%%~px%%~nx.jar"
mkdir "%~dp0\unpacked-jdk"
xcopy /s "%~dp0\jdk-out\.rsrc\1033\JAVA_CAB10\jdk" "%~dp0\unpacked-jdk"
cd /d "%~dp0"
cd /d "jdk-out\.rsrc\1033\JAVA_CAB9"
extrac32 110
xcopy /s "%~dp0\jdk-out\.rsrc\1033\JAVA_CAB9\src.zip" "%~dp0\unpacked-jdk"
cd /d "%~dp0"
rmdir /s /q "%~dp0\jdk-out"

Batch file for JDK 9

1
2
3
4
5
6
7
8
9
10
11
12
13
14
@echo off
set PATH=%PATH%;C:\Program Files\7-Zip\

rmdir /s /q "%~dp0\jdk-out"
rmdir /s /q "%~dp0\unpacked-jdk"
7z x %1 -o"%~dp0\jdk-out"
cd /d "jdk-out"
7z x tools.zip -ojdk
cd /d "jdk"
for /r %%x in (*.pack) do .\bin\unpack200 -r "%%x" "%%~dx%%~px%%~nx.jar"
mkdir "%~dp0\unpacked-jdk"
xcopy /s "%~dp0\jdk-out\jdk" "%~dp0\unpacked-jdk"
cd /d "%~dp0"
rmdir /s /q "%~dp0\jdk-out"

1. Run the script from the command line with the installer filename as the parameter:

1
unpack jdk-8u152-windows-x64.exe

or

1
unpack jdk-9.0.1_windows-x64_bin.exe

After completing these steps, you will find an unpacked-jdk directory containing the extracted JDK files.