Author |
Message
|
bijesh |
Posted: Mon Jun 15, 2009 5:15 am Post subject: Using £ symbol with SOAPRequest node |
|
|
Acolyte
Joined: 30 Jan 2007 Posts: 66
|
Hi,
Am getting an error while trying to send a request, that contains £ symbol in it, by using a SOAPRequest node.
Did anybody faced this scenario before or can anybody throw any light s on it?
Thansk n' Regards,
Bijesh. |
|
Back to top |
|
 |
Vitor |
Posted: Mon Jun 15, 2009 5:24 am Post subject: Re: Using £ symbol with SOAPRequest node |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
bijesh wrote: |
Am getting an error while trying to send a request |
What error? Parser error? Stack overflow? Wailing ancestral voices?
What version of WMB? On what platform?
bijesh wrote: |
that contains £ symbol in it, by using a SOAPRequest node. |
What code page is the SOAPRequest in? Does that symbol exist in that code page? How is that symbol encoded in the message? Does IE (or other tool) claim the XML is well-formed? _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
bijesh |
Posted: Mon Jun 15, 2009 5:33 am Post subject: |
|
|
Acolyte
Joined: 30 Jan 2007 Posts: 66
|
Am using WMB version 6.1.0.2 in Solaris. I use CCSID 937 to create the SOAP request.
Am getting the following error from the fault terminal of the SOAPRequest node.
org.xml.sax.SAXParseException: Invalid byte 1 of 1-byte UTF-8 sequence. |
|
Back to top |
|
 |
Vitor |
Posted: Mon Jun 15, 2009 5:44 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
bijesh wrote: |
I use CCSID 937 to create the SOAP request. |
What code page is that?
bijesh wrote: |
Am getting the following error from the fault terminal of the SOAPRequest node.
org.xml.sax.SAXParseException: Invalid byte 1 of 1-byte UTF-8 sequence. |
You've of course satisfied yourself that this only happens when you try and include that symbol?
Slightly off topic, but why that symbol? Why not GBP? _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
bijesh |
Posted: Mon Jun 15, 2009 8:55 am Post subject: |
|
|
Acolyte
Joined: 30 Jan 2007 Posts: 66
|
oh..sorry...the CCSID used was 923...
AM getting the parser exception only when I try with £ symbol in it. There is a requirement for the £ symbol to be send as it is. That is the reason for not using GBP. |
|
Back to top |
|
 |
Vitor |
Posted: Mon Jun 15, 2009 9:37 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
bijesh wrote: |
There is a requirement for the £ symbol to be send as it is. That is the reason for not using GBP. |
That's circular - "the reason we have to send the symbol not the code is because we have to send the symbol not the code"!
The reason there are ISO standard currency codes is to avoid exactly this problem. I would theorise there's some feature in the SAX parser, but if the symbol has to be sent exactly then wrap it in a CDATA section. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
telecoda |
Posted: Tue Jun 16, 2009 12:15 am Post subject: |
|
|
Novice
Joined: 05 Feb 2008 Posts: 15
|
|
Back to top |
|
 |
rekarm01 |
Posted: Tue Jun 16, 2009 1:46 am Post subject: Using £ symbol with SOAPRequest node |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 1415
|
Vitor wrote: |
bijesh wrote: |
I use CCSID 937 to create the SOAP request. |
What code page is that? |
Traditional Chinese Mixed Byte EBCDIC. No '£' there.
bijesh wrote: |
oh..sorry...the CCSID used was 923... |
Where is the CCSID used? Between the client and message flow? In the message flow? Between the message flow and web service?
bijesh wrote: |
Am getting the following error from the fault terminal of the SOAPRequest node.
org.xml.sax.SAXParseException: Invalid byte 1 of 1-byte UTF-8 sequence. |
It's more likely the error is coming from the web service, and being returned to the SOAPRequest node.
If the message data is encoded as ISO 8859-15 (ccsid=923), then why does the SAX Parser think it is UTF-8 (ccsid=1208)?
Either the message sent to the web service is corrupt (the message header ccsid doesn't match the message data ccsid), or the web service is ignoring the message headers, and assuming UTF-8. Find out which, and fix it. |
|
Back to top |
|
 |
|