| <html> |
| <head> |
| <META http-equiv="Content-Type" content="text/html; charset=UTF-8"> |
| <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> |
| <link rel="stylesheet" href="../../../../../default_style.css" type="text/css"> |
| <link rel="stylesheet" href="../../../../../webtools/wtp.css" type="text/css"> |
| <title>test plan: Application Client Module validation</title> |
| </head> |
| <body> |
| <table width="100%" cellspacing="5" cellpadding="2" border="0"> |
| <tbody> |
| <tr> |
| <td width="60%" align="left"><font class="indextop">jst j2ee</font> |
| <br> |
| <font class="indexsub">test plan: Application Client Module validation</font></td><td width="40%"><img width="207" hspace="50" height="129" align="middle" src="../../../../../webtools/images/wtplogosmall.jpg"></td> |
| </tr> |
| </tbody> |
| </table> |
| <table width="100%" cellspacing="5" cellpadding="2" border="0"> |
| <col width="16"> |
| <col width="*"> |
| <tbody> |
| <tr> |
| <td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Intoduction</font></b></td> |
| </tr> |
| <tr> |
| <td valign="top" align="right"> </td><td valign="top"> |
| <p>Validation on J2EE modules can be manual or automatic. To run it manually you need to select the J2EE module, right click and select <b>Run |
| Validation</b> on the pop up menu. The automatic validation is triggered during a full build or an incremental build if auto build preference is turned on there is delta i.e a change in one of the resources in the modules. The validators that are registered to run on a J2EE module can be seen on the validation properties page. <br> |
| |
| <br> |
| |
| </p> |
| </td> |
| </tr> |
| <tr> |
| <td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Steps</font></b></td> |
| </tr> |
| <tr> |
| <td valign="top" align="right"> </td><td valign="top"> |
| <p> |
| |
| <ol> |
| The Application Client Validator validates J2EE 1.2, 1.3 and 1.4 specification |
| artifacts and other artifacts that are related to the workbench for |
| Application client modules or an App Client(jar) archives. |
| For each of the validated scenario if an error condition is found the validator |
| puts out a Error, Warning or Informational message in the problems view based on |
| the severity of the error condition. Here are the list of artifacts and how to |
| validate these artifacts. <br> |
| |
| <br> |
| |
| <br> |
| |
| |
| <li> |
| Create and App Client module and delete the default main class created and the <b>Main-Class: Main</b> entry from the MANIFEST.MF file. |
| <br> |
| <br> |
| Result: Ensure a validation appears for the missing main class in an app client that is required for an app client as per spec., |
| </li> |
| |
| <br> |
| <br> |
| |
| <li> |
| Test project/module mismatch: Create a 1.2 and 1.3 application client project. Copy the 1.2 header from the xml file into the xml file of the 1.3 project, and vice-versa. You should get validation errors. |
| </li> |
| |
| </ol> |
| |
| </p> |
| </td> |
| </tr> |
| </tbody> |
| </table> |
| </body> |
| </html> |
