web server - Borland Technical Publications

General syntax and usage
General syntax and usage
The following table shows the currently defined Ant tasks and their relationship to the
equivalent command line tools.
Ant task name Equivalent command line Function
appclient appclient Runs a client application.
idl2java idl2java Converts IDL to Java classes.
java2iiop java2iiop Executes the java2iiop command.
iastool iastool Runs iastool.
Generally the BES Ant task uses the same pattern as the command-line tool
equivalent.
Name-value pair transformation
All name-value pair command line arguments can be transformed into Ant task
attributes. The name-value pair command-line arguments should be translated into
equivalent XML attributes. For example, the command line:
iastool -verify -src cart_beans_client.jar -role DEVELOPER
translates into the Ant task:
Name-only argument transformation
All name-only command-line arguments can be transformed into boolean type Ant task
attributes. For boolean-style attributes, such as -nowarn, use the default usage of the
attribute, according to the usage documented for each of the command line tools. See
Chapter 29, “iastool command-line utility” for more information about iastool command
line attributes.
Note
For example, the following command sets the warn attribute to false:
iastool -verify -src cart_beans_client.jar -role DEVELOPER -nowarn -nostrict
The equivalent Ant task is:
It is not valid to use “warn” as an attribute in the Ant task. For instance, the following
line causes a syntax error:
****** INCORRECT SYNTAX!!! ******
Multiple File Arguments
Many commands either act on multiple files or have options which can point to multiple
files. There are several ways to achieve this functionality in the equivalent Ant task. For
example, the iastool -merge command:
iastool -merge -target build\client.jar -type lib client\build\local_client.jar
build\local_stubs.jar
284 BES Developer’s Guide