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
Bedrock Mission!

Learn more

View all

Sign in to view all badges

[AEM Gems Webinar] Accelerating Experience Manager as a Cloud Service development with Rapid Development Environments

Default Sling Script Error


Level 3

Hi everyone,

I am doing an update for a component in which I need to add a new class in the backend. On adding the class and making the required updates in the pom.xml files I am still getting the following error : Cannot get DefaultSlingScript: No use provider could resolve identifier

I also tried changing the name of the class and adding the packages in the pom. I even tried changing the artifactid from uppercase to lowercase however the error still persists : Cannot get DefaultSlingScript: Compilation errors in org/apache/sling/scripting/sightly/apps/DeviceSupportPage/components/content/helloworld/

Line 28, column 1289 : Only a type can be imported. resolves to a package

Line 55, column 2410 : Democlass cannot be resolved to a type

Can anyone please guide me on this as to why such an error comes on drag and drop of the component?

Thanks and Regards,

Bernadine Soman

smacdonald2008Feike Visser

4 Replies



this error 'No use provider could resolve identifier' normally means:

- class can't be found

- bundle is not active


Level 10

AGree with Feike - make sure you are referencing the correct fully qualified class name in the HTL code and the bundle that contains this class is in ACTIVE State.


Level 1

Please check the imports for the new class which you created.


I was getting the same error when I was creating a sling model (@Model(adaptables =Resource.class))and after analysing the code I found that there was an import 

import javax.annotation.Resource which was not correct. I replaced it with the correct one 
import and the issue got fixed.