I am checking with the TOUCH UI experts on this.

I do not believe AEM supports this. At least - i have never seen clientlibs used this way or read anywhere this was supported.

To get an EVENT Handler working on 6.3 - follow this article - see how we created a System user and SLing Mapping. Creating an Event Listener for Adobe Experience Manager 6.4 You will need to use a 6.3 UBER JAR file - not the 6.4 one in that article. The application logic that article does result in...

That could be a bug. I have never used it to develop components. I will check with the Community product team to see if anyone knows about this,

You can use the AEM Replication API to build workflows. See this HELPX article: Adobe Experience Manager Help | Replicating Adobe Experience Manager Content using the Replication API If you look at the API call - you can define the path: //Inject a ResourceResolver - make sure to whitelist the bund...

If you look at the Weekend tutorial, which is a great guideline for AEM development, there is no mention of using this framework. Adobe recommends HTL for component development. Core components are all HTL based.

This would require a custom component - it's not available of the box. For example - assume you have a youtube for this manner: Introduction to live streaming - YouTube Help You can build a custom AEM component that can display this. We have a HELXP article that shows you how to build a custom compo...

I do not believe this is supported at the dialog field level.

Using JSP as opposed to HTL will not make any diff to the component dialog.I strongly recommend that you go through the doc I posted. You will learn more about the GRANITE/CORAL resource types and more about HOW TO work with HTL - which reflects best practices.

Works like a charm. List HTL Output: Java backend (I used WCMUsePojo for this example): package com.aem.htl.core;import java.util.ArrayList;import java.util.HashMap;import java.util.List;import java.util.Map;import org.apache.sling.api.resource.Resource;import org.osgi.framework.FrameworkUtil;import...