Đang chuẩn bị nút TẢI XUỐNG, xin hãy chờ
Tải xuống
WebSphere Studio Application Developer part 59 provides integrated development tools for all e-business development roles, including Web developers, Java developers, business analysts, architects, and enterprise programmers. The customizable, targeted, role-based approach of WebSphere Studio Application Developer will be characteristic of all new products built on the WebSphere Studio Workbench. It is well integrated with WebSphere Application Server and provides built-in server test environments that can be used for testing and profiling Web applications | Debugging a Web application In this section we show how to debug a servlet running as part of a Web application. We will be using the ListAccounts.java servlet in the ItsoProGuideBasicWeb project for our example. This is the servlet that was developed in Creating dynamic Web resources on page 203. Setting breakpoints in a servlet Breakpoints are indicators to the debugger that it should stop execution at specific places in the code and let you step through it. Breakpoints can be set to trigger always or when a certain condition has been met. To add a breakpoint in the code do the following Open the Li stAccounts.java in the Java editor. Place your cursor in the gray bar along the left edge of the editor area on the line Banking banking new Banking . Double-click to set a breakpoint Figure 16-1 . A marker will be shown at the line. Figure 16-1 Add a breakpoint 554 WebSphere Studio Application Developer Version 5 Programming Guide Note Enabled breakpoints are indicated with a blue circle. If the enabled breakpoint is successfully installed in a class in the VM at runtime it is indicated with a check mark overlay. Right-click the breakpoint in the breakpoint view and select Breakpoint Properties from the context menu. A window opens where more detailed options about the breakpoint are displayed Figure 16-2 . Figure 16-2 Breakpoint properties The Enable Hit Count property when set causes the breakpoint to be triggered only when the lines has been executed as many times as the hit count specified. Once triggered the breakpoint is disabled. The other property of interest here is Enable Condition. If set then the breakpoint is reached only when the condition specified in the entry field evaluates to true. This condition is a Java expression. In our case select Enable Condition and enter customerNumber.equals 104 as the condition. The breakpoint will only be reached when you enter 104 as the customer ID. The Restrict to Selected Thread s list is only filled if a server is
