| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| XML Parser support |
« View previous topic :: View next topic » |
| Author |
Message
|
| nthepak |
 Posted: Tue Jan 20, 2009 9:28 pm Post subject: XML Parser support |
 |
|
Voyager
Joined: 19 Dec 2005
Posts: 79
Location: India
|
Hi all,
I have to parse the special characters like "&" and "€" from the input xml message using XML parser. But it seems from the testing that XML parser does not support these characters from the CCSID 819 or 923.
Can anybody tell me how can i solve this issue please.
_________________
BR,
Deepak N |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Wed Jan 21, 2009 12:19 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Before Kimbert gets in,
If you are using the XML parser then DON'T. Change it to the XMLNSC
The XML Parser (with that name) is depreciated.
You may want to consider converting the message when it is read. Check the documentation for the MQInput Node. You can specify what CCSID you want to convert it to.
You could always put part of the output from a Trace Node (using ${Root}) placed right after the MQInput Node here. If you include the PRoperties & MQMD the we can see the CCSID etc of the incoming message. This is always a great help in debugging this sort of thing.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| rekarm01 |
| Posted: Wed Jan 21, 2009 12:44 am Post subject: Re: XML Parser support |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| nthepak wrote: |
| I have to parse the special characters like "&" and "€" from the input xml message using XML parser. But it seems from the testing that XML parser does not support these characters from the CCSID 819 or 923. |
XML interprets the '&' (ampersand) as a markup delimiter; it needs to be escaped in the input message, (for example "&"), in order for XML to interpret it as a literal ampersand.
The "€" (Euro Symbol) does not exist in the character set for CCSID=819. Attempting to convert a Euro Symbol character from the input message to CCSID=819 will likely produce invalid XML characters.
The "€" (Euro Symbol) does exist in the character set for CCSID=923. As long as the input header's CCSID matches the input message, the XML parser should not have a problem with it.
For further help, please provide a small sample input message (with headers) that reproduces the problem, along with the actual error messages generated, and any relevant code. |
|
| Back to top |
|
|
| kimbert |
| Posted: Wed Jan 21, 2009 1:54 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| it seems from the testing that XML parser does not support these characters from the CCSID 819 or 923. |
Careful! This has nothing at all to do with XML parsing. Either code pages 819/923 contain your character, or they don't.
As rekarm01 says, some characters must be escaped if they appear in your XML. But that is not a message broker issue - it is required by the XML specification. Either way, your message flow does not need to care. In the message tree you will get back the original character ( assuming that you have solved the code page issue above ). |
|
| 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
|
|
|
|
