Core components classes/models in Eclipse

-
Finding Core Components Classes and Models in Eclipse

Finding Core Components Classes and Models in Eclipse

Date: March 07, 2020

Hello Everyone,

AEM provides a range of out-of-the-box components, such as lists, images, navigation, and more. Whether you’re developing custom components or enhancing existing ones, understanding the core components' implementation is crucial.

If you want to locate the core components' implementation classes and models in Eclipse or any other IDE, you’ll need to include specific dependencies in your POM file.

Steps to Locate Core Components Classes

  1. Add Dependencies in Your POM File

    To access the core components, you need to add dependencies to your project’s POM file.

    In the Parent POM of Your Project:

    <dependency>
  <groupId>com.adobe.cq</groupId>
  <artifactId>core.wcm.components.core</artifactId>
  <version>2.4.0</version>
  <scope>provided</scope>
</dependency>

    In the Core POM of Your Project:

    <dependency>
  <groupId>com.adobe.cq</groupId>
  <artifactId>core.wcm.components.core</artifactId>
</dependency>
  2. Locate the Implementation Classes

    After adding these dependencies, you can find the core components' implementation classes in your IDE. Typically, they are located under:

    Core/Maven dependencies/com.adobe.cq.wcm.core.components.models

By including the appropriate dependencies in your POM file, you can easily access and examine the core components' implementation classes and models. This is essential for both custom development and enhancing existing components.

I hope you found this guide helpful! If you have any questions or suggestions, please feel free to leave a comment below.

Tags: AEM, Core Components, Eclipse, Maven, Dependency Management, AEM Development

Comments

Post a Comment

Popular posts from this blog

AEM show/hide enable/disable dialog fields based on Checkbox

-
Image
Hello All, While developing AEM components we might need to show/hide or enable/disable fields in dialog based on Checkbox or on Select dropdown. I implemented this for Touch UI dialog in AEM 6.5. Thanks to my friend Sameer Gunjal who helped me here. Requirement : On the basis of checkbox, We are going to enable/disable textfields of the dialog. Steps:   Add Granite:class to the checkbox node and to the fields you want to disable.  Remember, We are going to use these same classes in JS.   2      Create a clientlib, to place our JS file in it.                     I have created a JS file with name listeners.js,        Put below JS in the file that you created.        (function($) {    "use strict";    $(document).on("dialog-ready", function() {    $(docume...
Read more

AEM Caching with Google Guava: Use Case, Importance, and Implementation

-
AEM Caching with Google Guava: Use Case, Importance, and Implementation AEM Caching with Google Guava: Use Case, Importance, and Implementation Caching is essential in optimizing the performance of web applications, and when it comes to Adobe Experience Manager (AEM), caching strategies can be implemented at various levels. One such powerful caching mechanism that developers can use within the AEM application itself is Google Guava caching . In this blog, we will explore why Google Guava caching is important, and how you can use it effectively in AEM, along with a practical use case. Why Caching Is Important in AEM AEM is a robust content management system, but its performance can be affected if multiple repetitive and expensive operations (like API calls, database queries, or service executions) are executed frequently. These operations increase the load on the AEM instances, reduce response times, and impact the user experience. Caching ...
Read more

Creating a Chrome Extension for Easy Redirection to Multiple AEM Instances

-
Creating a Chrome Extension for Easy Redirection to Multiple AEM Instances As developers or content authors working with Adobe Experience Manager (AEM), you may often find yourself switching between different environments like local, dev, UAT, and production. Constantly typing or bookmarking URLs can be cumbersome, especially when you have multiple instances of AEM running. In this blog post, I will walk you through how to create a custom Chrome extension that allows you to easily switch between your AEM instances with a single click. Why a Chrome Extension? A Chrome extension is a handy tool to quickly access commonly used URLs. By setting up buttons for each AEM instance (local author, dev publish, UAT author, etc.), you can streamline the process of navigating between environments, saving time and minimizing errors. What You’ll Need Basic knowledge of HTML, JavaScript, and JSON. Chrome browser for testing. Your AEM instance URLs. Let’s dive into the steps! ...
Read more