| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| SOAPRequest Node not able to parse unicode characters |
« View previous topic :: View next topic » |
| Author |
Message
|
| Partha.Baidya |
 Posted: Mon Aug 13, 2018 2:08 pm Post subject: SOAPRequest Node not able to parse unicode characters |
 |
|
Voyager
Joined: 05 Nov 2009
Posts: 97
|
We have a message flow where we use SOAPRequest node to call a Master Data Management (MDM) Webservice. The webservice sometimes sends a faultstring containing Unicode characters. IIB SOAPRequest node's validation is set to "None". But IIB generates following exception
| Code: |
| xsd validation failure; An XML parsing error has occurred while parsing the XML document;1502;2;1;151;An invalid XML character (Unicode: 0xf) was found in the element content of the document.;/XMLNSC/{http://schemas.xmlsoap.org/soap/envelope/}:Envelope/{http://schemas.xmlsoap.org/soap/envelope/}:Body/{http://schemas.xmlsoap.org/soap/envelope/}:Fault/faultstring</faultstring> |
Is there any way that Unicode characters in SOAPRequest can be accepted? |
|
| Back to top |
|
 |
| joebuckeye |
| Posted: Tue Aug 14, 2018 4:48 am Post subject: |
|
|
Partisan
Joined: 24 Aug 2007
Posts: 365
Location: Columbus, OH
|
Unicode is just a method to define characters out there.
There plenty of Unicode characters that are valid in XML documents, 0xF is not one of them. It is a control character of some sort so not a printable character. The rough rule we use is if the character is not printable then it is not valid for use in an XML file. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Aug 14, 2018 6:12 am Post subject: Re: SOAPRequest Node not able to parse unicode characters |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Partha.Baidya wrote: |
| Is there any way that Unicode characters in SOAPRequest can be accepted? |
The problem is not with the SOAP but with the XML - you'd get the same problem if this document came in via MQ.
The parser is in all probability calling it "Unicode" because the XML has "utf-8" as it's encoding in the declaration. The problem is that '0xF' isn't valid in an XML document.
If the MDM web service you're calling is on Windows, it could be a BOM from a .NET construct. Bottom line, the system is sending a fault string with invalid XML characters in it and the only way to fix it is to fix their service.
If they don't believe it, get them to open their "fault string" in XMLSpy, Chrome, IE or anything else with an XML parser and watch it fail just like IIB does.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Partha.Baidya |
| Posted: Tue Aug 14, 2018 8:01 am Post subject: |
|
|
Voyager
Joined: 05 Nov 2009
Posts: 97
|
Thanks Vitor & joebuckeye for your responses.
We are talking with the backend MDM team if they can send only valid XML characters in the fault String. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
