1. Use System.out.println When running the OA Framework pages from jDeveloper itself, you can write debug messages using System.out.println. These debug messages will be displayed in the console of jDeveloper. Pro * Ease of use, as you simply enter free text messages * Debug messages simply appear without the need to set any profile optionsCons * Too much typing, which can be avoided when using the debugger of jDeveloper. * You can debug only those pieces of code that you suspect are causing the error. Unlike to this approach, using jDeveloper debugging, breakpoints can be set for exceptions/classes as well. 2. Use jDeveloper inbuilt Debugger This happens to be my favourite mechanism to debug OA Framework Pages, for the following reasons Pro * To get started just one breakpoint is required, as more and more breakpoints can be added in runtime itself. * You can set generic breakpoints, for example, you can set breakpoint on exceptions, w
To attain knowledge, add things everyday. To attain wisdom, remove things every day.