CRXDE Error | Community
Skip to main content
V
viswacq5
Level 3
October 16, 2015
Solved

CRXDE Error

  • October 16, 2015
  • 11 replies
  • 3515 views

Hi,

I'm working on the below exercise and i'm getting the output as expected.

http://helpx.adobe.com/experience-manager/using/using-sling-apis.html

But in CRXDE it throws errors may i know what is the root cause here because i'm eager to know whether it's code issue or crxde

Error:

Multiple annotations found at this line:
    - custom cannot be resolved 
     to a type
    - sling cannot be resolved

Also PFA Image

Thanks in advance!!

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 Ove_Lindström

There is really no need to be concerned of confused. The problem is NOT related to Adobe AEM, CRX or CRXDE. It is a classic Java resolving problem.

If you use a class, lets say custom.sling.Query, you need to have someone that declares that class in your development environment, either as source code or as a compiled class. All of the classes that are deployed in your CQ instance should be loaded into your IDE and added to the build CLASSPATH. Look at the CLASSPATH as an address to a warehouse where your classes are found at a specific shelf (custom.sling). What the IDE tells you is "yes, I know that you want that class, but I have talked to all my warehouses (that is the jar-files that contains the classes) and non-one stocks it. Could you please point me to the right place."

We use Maven to keep this kinds of dependencies and downloads the jar-files from the Adobe Repository.

11 replies

Show previous replies
O
Ove_LindströmAccepted solution
Level 6
October 16, 2015

There is really no need to be concerned of confused. The problem is NOT related to Adobe AEM, CRX or CRXDE. It is a classic Java resolving problem.

If you use a class, lets say custom.sling.Query, you need to have someone that declares that class in your development environment, either as source code or as a compiled class. All of the classes that are deployed in your CQ instance should be loaded into your IDE and added to the build CLASSPATH. Look at the CLASSPATH as an address to a warehouse where your classes are found at a specific shelf (custom.sling). What the IDE tells you is "yes, I know that you want that class, but I have talked to all my warehouses (that is the jar-files that contains the classes) and non-one stocks it. Could you please point me to the right place."

We use Maven to keep this kinds of dependencies and downloads the jar-files from the Adobe Repository.

Terms & ConditionsAccessibility statement

Loading footer...