Web service descriptions use XML Schema to describe the use of
simple and complex data types within a SOAP message. When utility programs
DFHLS2WS and DFHWS2LS generate Web services description from high level language
data structures, and high level language data structures from Web services
descriptions, they generate a mapping between the data types used in the two
places.
- Program DFHLS2WS maps high level language data types to XML Schema <simpleType> elements.
- Program DFHWS2LS maps <simpleType> elements to high
level language data types.
The two mapping are not symmetrical. This means:
- If you process a language data structure with DFHLS2WS, and then process
the resulting Web service description with DFHWS2LS, you should not expect
the final data structure to be the same as the one you started with. However,
the final data structure is logically equivalent to the one that you submitted
to DFHLS2WS.
- If you process a Web service description with DFHWS2LS, and then process
the resulting language data structure with DFHLS2WS, you should not expect
the XML Schema in the final Web service description to be the same as the
one you started with.
- In some cases, DFHWS2LS generates language data types that are not supported
by DFHLS2WS.
Language structures processed by DFHLS2WS must be correctly coded
according to the rules of the language as implemented in the language compilers
that CICS® supports.
DFHWS2LS
supports Web services descriptions that conform to WSDL version 1.1, with
the following restrictions:
Only SOAP bindings that use literal encodings are supported.
This means that the use attribute must be set to a value
of literal. use="encoded" is not supported.
- The only transport protocols supported by DFHWS2LS are HTTP, HTTPS and WebSphere® MQ
Series.
- Data type definitions must be encoded using the XML Schema Definition
language (XSD). Within the schema, data types used in the SOAP message must
be explicitly declared. DFHWS2LS does not support data types in the SOAP message
that are derived from other data types in the schema and that are not declared.
- The length of some keywords within the Web services description is limited.
For example, operation, binding and part names are limited to 255 characters
in length (in some cases the maximum operation name length may be slightly
shorter).
- Only one service element is supported for each binding element.
- Any SOAP faults defined in the Web service description are ignored. If
you want a service provider application to send a SOAP fault message, use
the EXEC CICS SOAPFAULT command.
Characters such as the opening angle bracket (<)
are reserved in XML. CICS handles these characters correctly when it maps
application data to the elements within a SOAP body. For example, < is
mapped to <.
The null
character (X'00') is not permitted in XML. If CICS maps application data containing
this character into a SOAP body, it is treated as a null-terminated string.