Mediations accessing SOAP headers should ensure that the SOAP header schema is made available to the SDO repository. This simplifies access to the header fields (see Web Services code example) and can provide a significant performance benefit. Normally the schema (.xsd file) for a SOAP header is already available to the application developer.
<soapenv:Header> <hns0:myClientToken xmlns:hns0="http://www.ibm.com/wbc"> <UseRoutingId>true</ UseRoutingId > <RoutingID>5</ RoutingID > </hns0: myClientToken > </soapenv:Header>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.ibm.com/wbc" elementFormDefault="unqualified"> <xs:element name=" myClientToken"> <xs:complexType> <xs:sequence> <xs:element name="UseRoutingId" type="xs:string"/> <xs:element name="RoutingID" type="xs:string"/> </xs:sequence> </xs:complexType> </xs:element> </xs:schema>
To insert the schema into the SDO repository, complete the following steps:
In this information ...Related concepts
Related tasks
| IBM Redbooks, demos, education, and more(Index) |