Using the JDeveloper Debugger

• It is very useful for pinpointing problems in your application.
• Set source breakpoints to pinpoint problems in custom code.
• Set exception breakpoints to stop when a particular exception is thrown.
• When breakpoint is encountered at run time, you can step through code and view values of variables.
• To run an application in debug mode, right-click and select Debug.

Notes:

Using the JDeveloper Debugger

JDeveloper’s integrated debugger is very useful for finding and fixing problems in your code. The following are some key places to set breakpoints:

Source breakpoint in the doIt() method of the JUCtrlActionBinding class (oracle.jbo.uicli.binding package): This is the method that executes when any ADF action binding is invoked, and you can step into the logic and look at parameters if relevant.

Method breakpoints in:

oracle.jbo.server.ViewObjectImpl executeQueryForCollection method: This is the method that is called when a view object executes its SQL query.

oracle.jbo.server.ViewRowImpl.setAttributeInternal method: This is the method that is called when any view row attribute is set.

oracle.jbo.server.EntityImpl.setAttributeInternal method: This is the method that is called when any entity object attribute is set.

A complete debugger lesson is beyond the scope of this course, but the OTN article Tips for Debugging ADF Applications Using JDeveloper contains useful information about debugging ADF applications.