If this service contains multiple Operations and it is implemented by the CICS® Web Services runtime environment, you can specify an optional WSBindSpec element. In that element, you can specify properties of the WSBind file representing multi-operation service. The WSBindSpec options provided on multiple Operations takes precedence over any WSBindSpec options that might be specified on individual Operations. That is, any WSBindSpec on individual Operations in multi-operation service is ignored.
The following is a sample of specifying multiple operations:
<EISProject name="BankPrj">
<EISService name="Bank">
.....
<Operation name="DepositFundsOperation">
....
</Operation>
<Operation name="WithdrawFundsOperation">
....
</Operation>
</EISService>
</EISProject>
The following rules apply when generating multiple Operations:
Table 1 shows the attributes for EISService.
| Fields | Description |
|---|---|
Attribute: name |
Specifies the name of the Web service. The name
of the Web Services Definition File (WSDL) that is generated uses
this name. The default value: The default is taken from the xsebatch command line parameter -w. |
Attribute: generateConverters |
Specifies whether to generate the converter set (request and response converters, driver). |
Attribute: generateSeparateXSD |
Specifies whether to generate a separate set
of XML schemas that define the message request
and response). Note: The "false" setting of this attribute is
meaningful only if generateWSDL is set to true. A value of false specifies
that the service definition file contains an embedded schema.
|
Attribute: generateWSDL |
Specifies whether to generate a service definition. |
Attribute: targetFilesURI |
Specifies the URI of the location where the
output files will be generated, relative to the top level project. The default value is: Value of targetNamespace, if specified. Otherwise it is set to file: //target.files |
Attribute: targetNamespace |
Specifies the URL of the target namespace. |
Attribute: type |
Specifies the relevant subsystem. |
<EISProject name="CICSSample">
<EISService name="CustomerInfo" type="CICS" targetNamespace="http://cics.sample"
targetFilesURI="file://my.files"
generateConverters="true"
generateSeparateXSD="false"
generateWSDL="true" >
</EISService>
</EISProject>