Verifier
The verifier validates the following types of J2EE component files:
- J2EE application .ear
- EJB .jar
- web component .war
- application client .jar
You can run the verifier three ways:
- from within the Application Deployment Tool
- as a command-line utility
- as a stand-alone GUI utility
To run the verifier from within the Application Deployment Tool, choose Verifier from the Tools menu. The following sections explain how to run the verifier the other two ways.
Command-Line Verifier
The command-line verifier has the following syntax:
verifier [options] <filename>
The filename argument is the name of a J2EE component file. The following table lists the options.
TABLE 10-5 Verifier Options
|
Syntax
|
Description
|
|---|
|
-v
|
displays verbose version of output
|
|
-o<output-file>
|
writes results to <output-file>, overriding default Results.txt file
|
|
-u
|
runs GUI utility
|
|
-<report-level>
|
determines whether warnings or failures are reported,
where <report-level> may be either a, w, or f:
a (all results)
w (warnings only)
f (failures only)
By default, only warnings and failures are reported.
|
Stand-Alone GUI Verifier
To run the stand-alone GUI verifier, follow these steps:
1. From the command-line, type:
verifier -u
2. To select a file for verification, click Add.
3. Select the radio button to indicate the report level:
- All Results
- Failures Only
- Failures and Warnings Only
4. Click OK.
5. The verifier lists the details in the lower portion of the screen.
Prev | Next
TOC | Index
Copyright © 2000 Sun Microsystems, Inc. All rights reserved.