|Oracle® Fusion Middleware Developer's Guide for Oracle JDeveloper Extensions
11g Release 2 (18.104.22.168.0)
Part Number E20067-04
|PDF · Mobi · ePub|
This chapter describes how to use the tools and features provided by Oracle JDeveloper to test and debug JDeveloper extensions.
This chapter includes the following sections:
You test and debug an extension by installing it and running it in a debug instance of JDeveloper.
JDeveloper provides you with a comprehensive debugger to test your code. For general information about debugging in JDeveloper, see "Debugging Applications" in Oracle Fusion Middleware User Guide for Oracle JDeveloper.
To debug an extension, you run it in JDeveloper. A new instance of JDeveloper opens in debug mode with the extension installed. If something is not working correctly then you can set breakpoints in your extension code to debug it.
When you have developed the code for your extension, you will want to try it out. To do this you install the extension and then run JDeveloper. A new instance of JDeveloper runs in debug mode for you to test your extension.
To run an extension in JDeveloper:
Run the extension using one of the following:
In the Application Navigator, select the extension project and from the main menu choose Run Extension.
From the context menu of the project in the Application Navigator, or in the source editor, choose Run.
From the Run menu on the JDeveloper toolbar choose Run Extension.
A new version of JDeveloper starts with the extension running in it.
With the extension running in a debug version of JDeveloper, you can text the functionality and use the JDeveloper debugging features to find and fix problems. For more information see "Debugging Applications" in Oracle Fusion Middleware User Guide for Oracle JDeveloper.
To debug an extension in JDeveloper:
Enter suitable breakpoints in your code.
Run the extension in JDeveloper in debug mode using one of the following:
In the Application Navigator, select the project and from the main menu choose Run > Debug Project.
From the context menu of the project in the Application Navigator, or in the source editor, choose Debug.
Click the Debug icon on the JDeveloper toolbar.
A new version of JDeveloper starts in debug mode with the extension running in it.
Is it necessary to include
Use this list of symptoms and solutions to resolve extension issues:
Symptom: Exception at startup.
Solution: Check stack trace and debug it.
Symptom: Extension does not load.
Solution: Check the Features dialog (available from the Tools menu) to make sure the extension is enabled when JDeveloper launches. For more information, see "How to Manage JDeveloper Features" in Oracle Fusion Middleware User Guide for Oracle JDeveloper.
Symptom: Class case exception.
Solution: For an extension that was written for an earlier version of JDeveloper, some code has not been migrated, or the extension was compiled against an older version of JDeveloper. Check to see that the extension has been migrated. For more information, see Section 1.5, "Migrating Extensions from Previous Releases."