DFHPI9666 E   A complexType can not contain more than one 'any' type. Problem found in type: '"typeName"'.

Explanation

An XML 'any' has been defined twice within the same construct in an XML schema. This is not supported by DFHWS2LS or DFHSC2LS except through the use of minOccurs and maxOccurs attributes.

This message may be issued if two xsd:any constructs appear in the same xsd:sequence. It may also be issued if a construct that is processed as though it were an xsd:any appears in that sequence. For example, if an abstract xsd:element with no substitution group appeared in the same sequence with an xsd:any then this message is issued.

System action

The Web services or XML assistant continues processing.

User response

Consider changing the WSDL document or XML schema to avoid this problem. For example, you could change the problematic XML construct for a different one that is supported. For example, the xsd:any construct is supported by both DFHWS2LS and DFHSC2LS and can be used as a replacement for most other constructs at mapping level 2.1 onwards. A change of this type can usually be made without breaking interoperability with partner processes that are implemented using the original XML schema or WSDL document. If changing or simplifying the XML schema or WSDL is not acceptable then other options exist:
  • If you are using DFHWS2LS, then at runtime level 2.1 onwards you can use the XML-ONLY parameter to opt-out of the CICS supplied XML transformation service. This results in a WSBind file being generated that tells CICS that the application will work directly with the SOAP Body in the DFHWS-BODY container.
  • If you are implementing a Web service provider application then you could consider writing your own XML capable SOAP application handler.
  • If you are implementing a Web service requester application then you could consider writing an XML capable application that uses the DFHPIRT channel linkable SOAP interface.
Other products may exist that can help process or omit the problematic XML constructs. For example, IBM's Rational Developer for System Z (RDz) product supports a "meet-in-middle" mapping scenario that allows omitting of specific XML constructs.

Module

DFHWS2LS, DFHSC2LS, DFHJS2LS

Destination

SYSPRINT



DFHPI9666E.html | Timestamp icon Last updated: Sunday, 4 June 2017