This conversation has been locked due to inactivity. Please create a new post.
This conversation has been locked due to inactivity. Please create a new post.
Solved! Go to Solution.
Views
Replies
Total Likes
In general all models/classes located under internal package are not exported by Core (Forms) Components bundles. This means you cannot use them directly, this is done by design.
In other words the way how you implementation is done is incorrect, this is why the issue occurs. The proper way to extend Core Components model is to use delegation pattern.
Here you can find some information with examples:
https://github.com/adobe/aem-core-wcm-components/wiki/Delegation-Pattern-for-Sling-Models
https://experienceleague.adobe.com/docs/experience-manager-core-components/using/developing/customiz...
Community Discussion Threads:
https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/com-adobe-cq-wcm-core-comp...
https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/extending-core-components/...
In general all models/classes located under internal package are not exported by Core (Forms) Components bundles. This means you cannot use them directly, this is done by design.
In other words the way how you implementation is done is incorrect, this is why the issue occurs. The proper way to extend Core Components model is to use delegation pattern.
Here you can find some information with examples:
https://github.com/adobe/aem-core-wcm-components/wiki/Delegation-Pattern-for-Sling-Models
https://experienceleague.adobe.com/docs/experience-manager-core-components/using/developing/customiz...
Community Discussion Threads:
https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/com-adobe-cq-wcm-core-comp...
https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/extending-core-components/...
Does that also work for extending form components ?
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies