wsdlURL | String Optional. Network accessible URL to a WSDL document or the path to and name of a WSDL on the same file system as the Integration Server.
| ||
wsdlString | String Optional. WSDL document as a string.
| ||
targetPackageName | String Name of the package in which to place the generated IS document types on Integration Server. | ||
targetFolderName | String Name of the folder in which to place the generated IS document types. Use the format folder.subfolder to specify the folder name. The folder must be empty or must not yet exist. | ||
generateheaderDocs | String Optional. Flag indicating whether the service should generate the documents corresponding to headers in the SOAP messages described in the WSDL document. Set to: true to generate the documents. This is the default. false to skip generating the documents. | ||
generateBodyDocs | String Optional. Flag indicating whether the service should generate the documents corresponding to SOAP body in the SOAP messages described in the WSDL document. Set to: true to generate the documents. false to skip generating the documents. This is the default. | ||
generateFaultDocs | String Optional. Flag indicating whether the service should generate the documents corresponding to SOAP faults in the SOAP messages described in the WSDL document. Set to: true to generate the documents. false to skip generating the documents. This is the default. | ||
generateXOPObject ForBase64Binary | String Optional. Flag indicating whether the service should generate fields of type com.wm.util.XOPObject corresponding to the xsd:base64Binary elements. Set to: true to generate fields of type com.wm.util.XOPObject. false to skip generating fields of type com.wm.util.XOPObject. This is the default. | ||
content ModelCompliance | String Optional. Flag that specifies how strictly the service represents content models from the XML Schema definition in the generated IS document types. Set to: Strict to generate the IS document type only if Integration Server can represent the content models defined in the XML Schema definition correctly. Document type generation fails if Integration Server cannot accurately represent the content models in the source XML Schema definition. Currently, Integration Server does not support repeating model groups, nested model groups, or the any attribute. If you select strict compliance, Integration Server does not generate an IS document type from any XML schema definition that contains those items. Lax to generate an IS document type that correctly represents the content models for the complex types defined in the XML schema definition, when possible. If Integration Server cannot correctly represent the content model in the XML Schema definition in the resulting IS document type, Integration Server generates the IS document type using a compliance mode of None. When compliance is set to lax, Integration Server will generate the IS document type even if the content models in the XML schema definition cannot be represented correctly. None to generate an IS document type that does not necessarily represent or maintain the content models in the source XML Schema definition. When compliance is set to none, Integration Server generates IS document types the same way they were generated in Integration Server releases prior to version 8.2. |
warnings | Document List Conditional. Contains any warnings encountered while generating IS document types from the provided WSDL. |