Troubleshooting
Problem
If a TypeCode in the InfoSphere MDM Server webservice XSD file extends "common:TypeCode" by using "xsd:complexContent", the extended type will fail on some XML parsers due to incorrect interpretation of XML Schema 1.0.
Symptom
A customer connected InfoSphere MDM Server v9.0.1 to a Tibco BusinessWorks environment using Web Services (SOAP over HTTP protocol). The customer was running into a problem with the way InfoSphere MDM Server formatted the Code Type tags in the XML requests. The results are parsing following XML validation errors on the Tibco side:
validation error: text not allowed in empty content ({com.tibco.xml.validation}COMPLEX_E_TEXT_NOT_ALLOWED_IN_EMPTY_CONTENT) at /outputMessage[1]/p388:GetPartyResponse[1]/result[1]/party[1]/status[1]/processingStatus[1]
This happened on base type:
<xsd:complexType name="TypeCode">
<xsd:simpleContent>
<xsd:extension base="xsd:string">
<xsd:attribute name="code" type="xsd:string"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
...with extended type below failing on Tibco XML parser due to incorrect interpretation of XML Schema 1.0:
<xsd:complexType name="ProcessingStatus">
<xsd:complexContent>
<xsd:extension base="common:TypeCode">
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
Log InLog in to view more of this document
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21445810