tailieunhanh - WebSphere Studio Application Developer Version 5 Programming Guide part 25

WebSphere Studio Application Developer part 25 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 | Figure 7-32 New JSP file wizard page 3 This page lets you supply page directive information for the JSP file It allows you to choose the scripting language Java is the preferred language but you can also choose Javascript if you would like set the imported types and packages and configure the set of directive attributes. If you do not select an attribute s check box it means that it will be assigned the default value which you can tell by checking the disabled radio group. First of all add the packages and to the imports list by clicking Import Package once for each package. Then because we do not need a session variable in our JSP page check the Create Session Variable box and set its value to false. Note that the default for a session variable in a JSP is true. Click Next to continue to the next page Figure 7-33 . 214 WebSphere Studio Application Developer Version 5 Programming Guide Figure 7-33 New JSP file wizard page 4 The wizard s fourth page lets you supply the JSP encoding DOCTYPE and style sheet information just like when we created our HTML page. Leave the options to their default values and click Next to continue to the last page Figure 7-34 . Chapter 7. Developing Web applications 215 Figure 7-34 New JSP file wizard page 5 This last page lets you select which JSP method stubs you would like the wizard to generate and whether or not to add deployment information to the Web project s deployment descriptor file. Because we do not need to add behavior to the life-cycle methods leave both init and destroy unchecked. Finally if you select the Add to box the JSP file along with its display name and any URL mappings and initialization parameters associated with the JSP file will be automatically included in the Web project s deployment descriptor file. We do not want to do that because our JSP s client is the ListAccounts servlet and not an external Web client. Note The File Name value provided in the first page of the .