The following table shows the tags (corresponding to classes) and
tag attributes (corresponding to class variables) used for externalizing client
Operation objects. The operation tag can be either "operation", a tag name
with a related class set in the toolkit definition file (such as MyOperation),
or a specific class name (such as myPackage.MyOperation). See Tag linking
for more information on the refFormat tag.
Table 1. operation or operation <ClassName> tag attributesAttribute |
Description |
id |
The name of the operation step. This is a mandatory attribute. |
implClass |
The name of the class the toolkit is to instantiate if the tag name
is "operation". This value overrides any definition for the operation in the
toolkit definition file. |
context |
The name of the operation context. |
serverOperation |
The name of the class of the server operation. |
serverOperationParentContext |
The parent context of the server operation. |
xVal |
The name of the class implementing the process for validating
a cross business operation. This class must implement the OperationXValidate
interface. By providing a specific class that implements the business validation
for the concrete operation, the applications can use a generic operation class
for more than one business operation yet invoke a concrete validation that
may be specific to each operation. |
Table 2. refFormat (FormatElement) tag attributesAttribute |
Description |
name |
The type of formatter required. The value of this attribute
is one of the following:- csRequestFormat (for requests)
- csReplyFormat (for responses)
|
refId |
The name of the formatter. |
Table 3. refOpSteps (OperationStep) tag attributesAttribute |
Description |
refId |
The name of the collection containing the operation
flow. |