At the Breaking Point

Debugging is very fundamental to successful enterprise application development. When an unexpected operation occurs in a Java program, an exception signals the problem. To locate the problem quickly, one can use an exception breakpoint to stop the debugger whenever a specific kind of exception is thrown. The starter workspace contains code that throw java.lang.StringIndexOutOfBoundsException because of a programming error. Oracle ADF simplifies problem-solving by letting one set breakpoints on key declarative constructs such as bindings and task flow activities. For example, one can set a breakpoint on a binding for a JavaServer Faces page or page fragment. To try this out, expand the ViewController project, its Web Content folder, and the Page Flows folder. When one uses the techniques to debug applications, it is important to remember that the debugger watch expressions, breakpoint conditional expressions, and expressions to log in to the console can involve any combination of member fields, method calls, and Java operators. One should be able to devise creative ways of using them in troubleshooting. After using the techniques explained here to debug explanations remember that the debugger watch expressions, breakpoint conditional expressions, and expressions to log in to the console can involve any combination of member fields, method calls, and Java operators. This helps users to also craft their own targeted diagnostic information during the breaking point.