Reference component - why deprecated

Forum|Forum|3 years ago
August 23, 2022
2 replies
1086 views

Hi folks,

I noticed the Reference foundation component recently. You can use it as a pointer to another configured component. Apparently it is being deprecated. Does anyone know why, are there drawbacks to working with it ?

thanks

Fiona

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

Best answer by ManviSharma

Hi,

> If a component is deprecated then an alternative option would be listed on the documentation link[0]. The alternative to the deprecated components would be the core components listed here[1].

[0] https://experienceleague.adobe.com/docs/experience-manager-65/release-notes/deprecated-removed-features.html?lang=en

[1]

https://experienceleague.adobe.com/docs/experience-manager-core-components/using/introduction.html?lang=en

Mohit_KBansal

Adobe Employee

With reference component, content management was a challenge, as reused content is part of main hierarchy/pages. AEM has a better and cleaner approach to using Experience Fragments, which is a good replacement for reference components.

F

fionas76543059Author

Level 6

thanks, that makes sense

ManviSharma

Accepted solution

Adobe Employee

Hi,

> If a component is deprecated then an alternative option would be listed on the documentation link[0]. The alternative to the deprecated components would be the core components listed here[1].

[0] https://experienceleague.adobe.com/docs/experience-manager-65/release-notes/deprecated-removed-features.html?lang=en

[1]

https://experienceleague.adobe.com/docs/experience-manager-core-components/using/introduction.html?lang=en