Level 7

About the component sling resolution in AEM FORM (6.5)

Forum|Forum|3 years ago
January 6, 2023
1 reply
1048 views

Hello,

Could some one help me as how will a sling call will be resolved for a component based on sling resource for a AEM form component

I see the below nodes for a component ,what does each node specify and can we remove any of this nodes will it still work??

Component node

- clientlibs

-cq:dialog

-cq:styleConfig

-cq:template

-formatters

-validators

-init.jsp

-widget.jsp

Which above files could be replaced to HTL based slightly .html files and component will still work

Regards,

Srinivas

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

Pulkit_Jain_

Adobe Employee

@srinivas_chann1

Sling resource resolution is a multi-step process and you can refer to these help docs[0][1] to understand - how a URL is mapped to corresponding jcr node in AEM and how Sling resource resolution is done.

Depending on the component, there could be different child nodes/properties but its not advisable to remove any property from the OOTB components. You can read more about these child nodes/properties here[2].

One can develop any component using HTL instead of JSP, with an exception of Granite UI Foundation Form Fields that still require the use of JSP. For an expert advise on this, you can check here- https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/ct-p/adobe-experience-manager-community

[0] - https://sling.apache.org/documentation/the-sling-engine/servlets.html#servlet-resolving

[1] - https://sling.apache.org/documentation/the-sling-engine/url-decomposition.html

[2] - https://experienceleague.adobe.com/docs/experience-manager-65/developing/components/components-basics.html?lang=en#properties-and-child-nodes-of-a-component