| <?xml version="1.0" encoding="UTF-8"?> |
| <?xml-stylesheet type="text/xsl" href="../../../../wtp.xsl"?> |
| <html> |
| <head> |
| <meta name="root" content="../../../../.." /> |
| <title>test plan: Application Client Module validation</title> |
| </head> |
| |
| <body> |
| <h1>jst j2ee</h1> |
| |
| <h2>Intoduction</h2> |
| <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> |
| |
| <h2>Steps</h2> |
| <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> |
| |
| |
| </body> |
| </html> |
