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. Note: All the XML Schema definitions and WSDL documents imported by or included by the target WSDL document must be network accessible or on the local file system as well. |
wsdlString | String Optional. WSDL document as a string. Note: All the XML Schema definitions and WSDL documents imported by or included by the target WSDL document must be network accessible or on the local file system as well. |
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: ![]() ![]() |
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: ![]() ![]() |
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: ![]() ![]() |
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: ![]() ![]() |
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: ![]() 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. ![]() 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. ![]() 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. |