Debugging OSGi Java Code in AEM: A Simple Guide

-
Debugging OSGi Java Code in AEM

Debugging OSGi Java Code in AEM: A Simple Guide

Steps to Debug OSGi Code in AEM

  1. Start AEM in Debug Mode 
    java -Xmx2g -agentlib:jdwp=transport=dt_socket,address=5402,server=y,suspend=n -jar cq-author-p4502.jar -gui

    Note: Replace cq-author-p4502.jar with your specific jar file name. Ensure the port number (5402 in this example) matches the one you use.

  2. Set Up Eclipse for Remote Debugging

    - Open Eclipse and navigate to Debug Configurations by selecting Run -> Debug Configurations.

    - Choose Remote Java Application and click on New Launch Configuration.

  3. Configure Debug Settings

    - Enter a name for your configuration.

    - Set the Host to localhost (or your server’s IP address if remote).

    - Set the Port to 5402 (or the port number you specified when starting AEM).

    - Click Apply to save your settings.

  4. Set Breakpoints and Start Debugging

    - Open your Java code in Eclipse and set breakpoints where needed.

    - Click the Debug icon to launch your configuration.

    - Refresh your AEM page to trigger the breakpoint.

  5. Control Code Execution

    - Use F6 (Step Over) to go through your code line by line.

Happy debugging! If you have any questions or need further assistance, feel free to reach out. 😉

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