Proxy component until when it's treated as Core component | Community
Skip to main content
rsl_lucky
rsl_lucky
Level 4
September 29, 2021
Solved

Proxy component until when it's treated as Core component

  • September 29, 2021
  • 3 replies
  • 1048 views

Hi All,
Have a Proxy Text component created from AEM core components features as is. Now need to enhance proxy Text component with few dialog field updates as per our new requirement. If we customize Proxy with new updates in it then, will it still be treated as a core or it becomes a custom component.?

 

Till when we say we used Core components for our functionality ???

 

Thanks.

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 arunpatidar

Hi,

The component will take update till you have the resource superType. If you remove the sling:resourceType then it will become a local component.

The new component with the local changes will be a custom component with inherited nodes/properties

https://helpx.adobe.com/experience-manager/using/extend_jave_corecomponents.html

 

And you can say you used extended core component 😉

3 replies

Sanjay_Bangar
Community Advisor
Sanjay_BangarCommunity Advisor
Community Advisor
September 29, 2021

Hi @rsl_lucky ,

                       When  you  have created component/ proxy component in your project repository then it becomes custom component .

Kr,

Sanjay

    arunpatidar
    Community Advisor
    arunpatidarCommunity AdvisorAccepted solution
    Community Advisor
    September 29, 2021

    Hi,

    The component will take update till you have the resource superType. If you remove the sling:resourceType then it will become a local component.

    The new component with the local changes will be a custom component with inherited nodes/properties

    https://helpx.adobe.com/experience-manager/using/extend_jave_corecomponents.html

     

    And you can say you used extended core component 😉

    Arun Patidar
      ArpitVarshney
      Community Advisor
      ArpitVarshneyCommunity Advisor
      Community Advisor
      September 29, 2021

      Hi @rsl_lucky 

       

      It would make more sense to say it as "Extended Core Component" as @arunpatidar  mentioned, as the component is connected to parent component via resource superType. and any changes in core component will be reflected in your component automatically with the upgrade.

       

      Regards,

      Arpit Varshney

        Terms & ConditionsAccessibility statement

        Loading footer...