user manual

Chapter 29: iastool command-line utility 371
Using the iastool command-line tools
The verification process supports the following roles that correspond to a
phase in the application's life cycle and the appropriate level of verification
(similar to the J2EE role definitions):
■
Developer: This is the lowest verification level. All xml is checked for
syntax as well as standard and proprietary keywords relevant to the current
archive type. Consistency across the archive is checked, but no external
resources are verified at this level.
■
Assembler: Once the archives are individually verified and are correct,
other resources built into an application will start to be verified. For
example, this level will verify the existence and correctness of URIs
(Uniform Resource Identifiers), but not EJB or JNDI links.
■
Deployer: (the default) All checks are turned on. EJB and JNDI links are
checked at this level as well as the operational environment in which the
application is to be deployed.
Supported archive types are EAR, EJB, WAR, JNDI, and Client JARs. The
typical archive verification process includes the following checks:
■
A pass over the XML, checking for correct XML syntax.
■
Verification of the semantics of the standard and proprietary XML
descriptors, and the compliance with their required descriptors for each
supported archive type.
Verification always occurs in a hierarchical fashion, starting with the top
module, then recursively working through its submodules, and finally checking
for inter-archive links.
Syntax
-verify -src <srcjar> [-role <DEVELOPER|ASSEMBLER|DEPLOYER>] [-nowarn]
[-strict] [-classpath <classpath>]
Default Output
By default, verify reports nothing (for example, if no errors are found in the
specified module).