Not able to extends PageImpl.java from Core Components

Avatar

Avatar

Reini-

Avatar

Reini-

Reini-

25-09-2020

Hello,

 

I have to extend the existing implementation of com.adobe.cq.wcm.core.components.internal.models.v2.PageImpl, because I have to provide an additional css class to getCssClassNames method based on some settings in page properties. But its not possible to extend this class because this class is in the "internal" package. And as I know this will not be exported to other OSGi bundles.

 

For me this means, I have to copy the code from v2.PageImpl and v1.PageImpl and all other used classes which are also in "internal" package to my project. In my opinion this kind of implementation of core components does not make any sense, because it blocks developers to reuse existing code.

 

Or does somebody have a solution for this problem?

 

regards

Reini

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar

vmadala

Avatar

vmadala

vmadala

26-09-2020

Hello @Reini- 

Since core implemented classes are in the internal package, you can't extend these classes into your package.
This is expected behavior, you can get more info about this limitation here https://github.com/adobe/aem-core-wcm-components/issues/503
I would suggest here, you don't need to copy all the code from the core implementation class (PageImpl.java),
you can use the Delegation pattern for sling models. For this, you have to write a model class and  you can add you're own methods something like below

public class MyPageImpl implements Page  {

  @Self
@Via(type = ResourceSuperType.class)
private Page page;  // here you'll get the actual implementation class of PageImpl

@Override
public String getAppResourcesPath() {
return page.appResourcesPath;
}


public String getCssClassNames() {
return "my-css-class-name"
}

}

You've to use this model in your HTL file and you're component must inherit from the core page component.


Thanks,

Venkat.M

Answers (4)

Answers (4)

Avatar

Avatar

Arun_Patidar

MVP

Total Posts

2.9K

Likes

1.1K

Correct Reply

839

Avatar

Arun_Patidar

MVP

Total Posts

2.9K

Likes

1.1K

Correct Reply

839
Arun_Patidar
MVP

27-09-2020

You have to extend the interface, not the actual implementation as suggested by @vmadala 

Avatar

Avatar

Shashi_Mulugu

MVP

Avatar

Shashi_Mulugu

MVP

Shashi_Mulugu
MVP

26-09-2020

@Reini- if you want to inject any new css classes, please use page level style system which is OOTB. Refer to below community post for reference:

 

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/don-t-understand-cssclassn...

Avatar

Avatar

Jörg_Hoh

Employee

Total Posts

3.0K

Likes

952

Correct Reply

1.0K

Avatar

Jörg_Hoh

Employee

Total Posts

3.0K

Likes

952

Correct Reply

1.0K
Jörg_Hoh
Employee

25-09-2020

Hi,

It is the decision of the core component team to hide the implementation classes. My recommendation is to have that discussion at the core components repository at https://github.com/adobe/aem-core-wcm-components/issues.

You get the best answers there for this question.

Avatar

Avatar

Manjunath_K

Avatar

Manjunath_K

Manjunath_K

25-09-2020

.