Free Trial

Safari Books Online is a digital library providing on-demand subscription access to thousands of learning resources.

Share this Page URL

Chapter 10. Hints and tips > Handling undefined XML (xsd:any) - Pg. 233

strcpy(names[1].name,"Another_User"); /*...etc...*/ /*Using a global function to generate a unique container name*/ memcpy(name_container,get_container_name(),16); /*Add the concatenation to a container*/ EXEC CICS PUT CONTAINER(name_container) FROM(names) FLENGTH(sizeof(struct Name) * 5); /*populate the name_cont and name_num variables*/ memcpy(name_cont,name_container,16); name_num = 5; } 10.4 Handling undefined XML (xsd:any) Some WSDL documents allow sections of arbitrary well-formed XML to be included within the application data. For example, you could embed an XHTML document within the body of the SOAP message. Where this technique is used the WSDL will use either an xsd:any tag, or an xsd:anyType data type. Prior to mapping level 2.1, DFHWS2LS did not support these constructs. At mapping level 2.1 they are supported using a pass-through technique that allows the application to handle that subset of the SOAP directly as XML. For example, consider the fragment of WSDL viewed in RDz shown in Figure 10-3 on page 234. It specifies an optional undefined XML tag might appear on the end of an xsd:sequence. This is a technique that can be used to support future evolution of the WSDL. If version 2 can add something specific to the end of the list, the resultant SOAP message will still validate with respect to the original WSDL. Chapter 10. Hints and tips 233