WebSphere Studio Application Developer part 16 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 | Refactoring preferences In the Refactoring preferences page located in Window - Preferences - Java - Refactoring you can select the default level for problems to be displayed when you are carrying out a refactoring without a preview Figure 5-29 . Figure 5-29 Refactoring preferences The set of radio buttons is used to indicate what type of error reporting you want to see in the refactoring dialog. These options are listed in order of severity. By default Application Developer will display any error that would occur if the refactoring is performed. If you check the option Save all modified resources automatically prior to refactoring any outstanding changes will be saved without displaying a prompt. Refactoring example The following example of a refactoring operation assumes that you want to rename a class in your Java program. To initiate the renaming simply select the class and select Refactor - Rename in the context menu. The Refactoring wizard is displayed where you rename the class and select the appropriate refactoring settings Figure 5-30 . 124 WebSphere Studio Application Developer Version 5 Programming Guide Figure 5-30 Refactoring wizard Enter the new name for the class and click Next. If there are any files with unsaved changes in the Workbench and you have not indicated in the preferences that the save should be done automatically you are prompted to save these files before continuing the refactoring operation. If problems more severe than the default level set in the refactoring preferences are anticipated then the problems page is displayed Figure 5-31 . If the problems are severe the Next and Finish buttons are disabled and the refactoring must be aborted until the problems have been corrected. If the buttons are enabled you can select whether to accept the problems and continue or to cancel the refactoring operation. Figure 5-31 Refactoring problems Selecting Next at this point displays a window showing what actions will be performed during the .
