web server - Borland Technical Publications

Other features
Other features
Borland Enterprise Server includes a number of extra features in the VisiClient
container in addition to the requirements for the J2EE specification. These include:
■
■
User Transaction interface: This is available in the java:comp/env name space
and can be looked up using JNDI. It supports transaction demarcation, and
propagation.
Client Verify Tool: This runs on standalone client JARs or client JARs embedded in
an EAR file. The verify tool enforces the following rules:
■
■
■
■
■
The manifest file in the client JAR has the main class specified.
The JAR/EAR is valid (it has the correct required manifest entries).
ejb-refs are valid (that is, a JNDI name for the target EJB is specified in the
Borland-specific file).
If ejb-ref is an ejb-link, then the archive should be an EAR file. There must also
be an EJB with the same name as the ejb-link value in the EAR file.
Resource references are valid.
Using the Client Verify tool
The following command line demonstrates the use of the Client Verify tool:
iastool -verify -src -role
Usage examples of Client Verify tool:
iastool -verify -src sort.jar -role DEVELOPER
iastool -verify -src sort.ear clients/sort_client.jar -role DEVELOPER
For more information see Chapter 29, “iastool command-line utility” on the available
options.
Chapter 12: The VisiClient Container 105