For a SOAP header entry or SOAP fault detail, the WSDL Analyzer provides similar documentation for complex data. If it can identify a temp-table or ProDataSet that matches the SOAP header entry, it simply provides the appropriate static ABL definition. If a dynamic temp-table or ProDataSet mapping is possible, the WSDL Analyzer also documents this fact with any appropriate explanatory notes.

For these SOAP elements, you never access a temp-table or ProDataSet directly. For a response header, you must access the header entry XML and use an ABL temp-table or ProDataSet READ-XML( ) method to transform the XML into temp-table or ProDataSet data, which you can then access as ABL data types. For a request header, you can create the header data in the corresponding temp-table or ProDataSet and transform it to the header entry XML using a temp-table or ProDataSet WRITE-XML( ) method. For SOAP fault detail, you must access the SOAP fault detail XML and use an ABL temp-table or ProDataSet READ-XML( ) method to transform the XML into temp-table or ProDataSet data, which you can then access as ABL data types. Again, if no temp-table or ProDataSet mapping is possible, you must use the ABL DOM or SAX features to access the XML for a header entry.

For more information on how to use ABL to work with complex data passed as a SOAP header entry, see Handling SOAP Message Headers in ABL For more information on how to use ABL to work with complex data passed as SOAP fault detail, see Handling Errors in ABL Requests to OpenEdge SOAP Web Services.