I've included the Forms Core Components in one of our AEM 6.5 projects. For detailed changes and procedures, you can refer to this GitHub commit: https://github.com/MahediSabuj/aem-react-spa/commit/b302dd8cd87c48b5b93509c050099a7a3dbf02f4 If you're using AEMaaCS, you should replace "aemfd-client-sdk...

To fetch multifield data using fieldName, you need to make few adjustments readJson = resource.getResourceResolver().getResource( currentNode.getPath() + "/" + this.fieldName); listArr = readJson ? readJson.listChildren() : {};https://varunaem.blogspot.com/2019/06/javascript-use-api.html  

Can you confirm whether jsonDeserializer.js returns the expected values? You need to define context for few properties such as image src. https://github.com/adobe/htl-spec/blob/master/SPECIFICATION.md#121-display-contextAlso, Please share your jsonDeserializer.js implementation. However, I would rec...

You need to make few updates in the component dialog:1. In the multifield node, include the property "composite" with value "{Boolean}true" .  <highlights jcr:primaryType="nt:unstructured" composite="{Boolean}true" <!-- Add this line --> sling:resourceType="granite/ui/components/coral/foundation...

You should declare DemoServlet as a Sling Model using the @Model annotation. Here's an example: @Model( adaptables = SlingHttpServletRequest.class, adapters = { DemoModel.class }, defaultInjectionStrategy = DefaultInjectionStrategy.OPTIONAL ) public class DemoModel { ..... } 

I would recommend to create a dedicated "common.core" module to include all third-party dependencies. Afterward, you can embed the "common.core" artifact into all pom.xml.Please make sure you've added third-party dependencies to both root and core pom.xml as well.https://myaemlearnings.blogspot.com/...

Could you also include "flying-saucer-pdf" as a dependency <dependency> <groupId>org.xhtmlrenderer</groupId> <artifactId>flying-saucer-pdf</artifactId> <version>9.2.2</version> </dependency>https://github.com/flyingsaucerproject/flyingsaucer/blob/main/flying-saucer-pdf-osgi/pom.xml  

Can you try using below OSGI compatible version<dependency> <groupId>org.xhtmlrenderer</groupId> <artifactId>flying-saucer-pdf-osgi</artifactId> <version>9.2.2</version> </dependency>https://mvnrepository.com/artifact/org.xhtmlrenderer/flying-saucer-pdf-osgi

Checking the wiki page at AEM Core Components https://github.com/adobe/aem-core-wcm-components/wiki/Simplified-Components-Proposal, and it seems useful for AEM SPA and Headless implementations.Can anyone provide an update for this implementation?

In the majority of instances involving third-party bundles, the resolution of the Maven dependency in both the main pom.xml and the core pom.xml results in the successful inclusion of the required bundle.Nevertheless, there are situations where this automatic process does not occur as expected. In s...