Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

How can resolved "org.apache.sling.scripting.sightly.render.ObjectModel Cannot access method configured on object com.adobe.cq.wcm.core.components.internal.models.v1.ExperienceFragmentImpl"

Avatar

Avatar
Boost 1
Level 1
Woobi
Level 1

Like

1 like

Total Posts

3 posts

Correct Reply

0 solutions
Top badges earned
Boost 1
Validate 1
Shape 1
View profile

Avatar
Boost 1
Level 1
Woobi
Level 1

Like

1 like

Total Posts

3 posts

Correct Reply

0 solutions
Top badges earned
Boost 1
Validate 1
Shape 1
View profile
Woobi
Level 1

17-03-2021

AEM:  as cloud Service

 

I'm getting below error in the error.log when using content fragment in my content pages. 

 

org.apache.sling.scripting.sightly.render.ObjectModel Cannot access method configured on object com.adobe.cq.wcm.core.components.internal.models.v1.ExperienceFragmentImpl@10ff42d2
java.lang.reflect.InvocationTargetException: null

...

 

Kindly please let me know what causing this error and how to resolve it. 

 

View Entire Topic

Avatar

Avatar
Ignite 1
Level 4
davidjgonzalezzzz
Level 4

Likes

54 likes

Total Posts

60 posts

Correct Reply

20 solutions
Top badges earned
Ignite 1
Give Back 5
Give Back 3
Give Back 10
Give Back
View profile

Avatar
Ignite 1
Level 4
davidjgonzalezzzz
Level 4

Likes

54 likes

Total Posts

60 posts

Correct Reply

20 solutions
Top badges earned
Ignite 1
Give Back 5
Give Back 3
Give Back 10
Give Back
View profile
davidjgonzalezzzz
Level 4

17-03-2021

UPDATE: i misread this error (thought you were referencing the impl class, but really it looks like the HTL cannot instantiate the Sling Model via the interface reference (which is bound to that Impl). See Arun's answer below.

 

You are trying to access an INTERNAL class as denoted by the "internal" package name: com.adobe.cq.wcm.core.components.internal.models.v1.ExperienceFragmentImpl

Classes under internal packages are considered internal implementation details of the project and cannot be used by Consumer code. 

 

In AEM development, typically you will have public interfaces you can code against, but the implementation (usually post-fixed with Impl) will not be exported by the bundle therefore not available for you to directly use.

 

Instead of using the Impl directly in Core Components, you should leverage the Sling Model Delegation pattern described on the Core Components Github project: https://github.com/adobe/aem-core-wcm-components/wiki/Delegation-Pattern-for-Sling-Models