Originally posted by: SystemAdmin

Hi All,

I am having issue in parsing a xml message with xsi:type. Here is the sample message

<ns2:customer xmlns:ns2="http://service.Common/2008/">
<ns3:Key xmlns:ns3="http://service/">
...
</ns3:Key>
<ns4:extendedList xmlns:ns4="http://service.common/2008/05/">
<ns4:extendedInfo xsi:type="ns4:ExtendedInfo_Type">
<ns4:Reference>
<ns5:account ..
...
</ns5:account>
</ns4:Reference>
...
</ns2>

I get the error

external Parser returned Error:
TYPE X'0002' (Error (-9), "XMLParser: Could not find type to assign XML data."
No type to assign data was found
element name: ExtendedInfo_Type, namespace: http://service.common/2008/05/, current input data offset: 1649

if I remove the xsi:type attribute, it works fine.

Any fix for this pls?
Thanks in advance!!

-Mahesh
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: zamzam

Hi maheshpn,

i have the same problem.

I imported an XSD with 'import' + namespace tag and i tried to execute process :

• import : ok (contains all tags for all files)
• compilation : ok (no error)
• execution : ko (see log)

It seems that WTX checks with the main XSD but doesn't see other types in imported XSD file ...
Why an input card as to be associated with an unique XSD if many are needed?

Log :

(Level 1: Offset 57, len 545, comp 2 of 2, #1, DI 000000000014:)
Data at offset 57 ('<ReceiveXMLMessa...') was found to be of TYPE
X'0008' (Global XSD).

(Level 1: Offset 57, len 545, comp 1 of 2, #1, DI 000000000015:)
External Parser returned Error:
TYPE X'0002' (Error (-9), "XMLParser: Could not find type to assign XML data."
No type to assign data was found
element name: AppHdr, namespace: urn:swift:xsd:$ahV10, current input data offset: 571

Error (-9), "XMLParser: Could not find type to assign XML data."
No type to assign data was found
element name: MsgRef, namespace: urn:swift:xsd:$ahV10, current input data offset: 584

Error (-1), "XMLParser: Input XML data is invalid."
There is a mismatch between t).

External Parser returned Error

End of Validation messages for INPUT CARD 1.
End of Execution messages.
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange