| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| XML Message |
« View previous topic :: View next topic » |
| Author |
Message
|
| chris boehnke |
 Posted: Mon Feb 28, 2011 7:29 pm Post subject: XML Message |
 |
|
Partisan
Joined: 25 Jul 2006
Posts: 369
|
Hi Guys,
My message has below special characters and it throws xml parsing error when I drop the message to a queue. I would like to know if the below characters are supported by XML.
Thanks
Chris |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Mon Feb 28, 2011 8:45 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Supported by XML, I would think yes, but you might have to use the escaped form. The easiest way to test this is to allocate the character to the value of an XML element in the broker and look at the serialized message in MQ.
If the character has been escaped than that is what you need to do...
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Mon Feb 28, 2011 10:42 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
None of the characters you mentioned are on the list of XML Must BE escaped characters.
There are many places where you can find the list. Here is one.
[url]
http://stackoverflow.com/questions/1091945/where-can-i-get-a-list-of-the-xml-document-escape-characters
[/url]
What I suspect is that the original CCSID encoding for these characters is wrong.
[url]
http://en.wikipedia.org/wiki/List_of_XML_and_HTML_character_entity_references
[/url]
Will help.
What you need to do is to find out the raw (hex) values of the errant characters.
You can then map these using the w3c (and other places) into a CCSID table.
A common mistake is to code the body in ISO-88590-1(,2,3,...15 etc) but then use the default CCSID of the QMGR to send the message. This may be 1208, 923, 437 etc. All will have varying degrees of success with the variable payloads. Some messages will pass ok others will blow up in your face.
The proper solution (and one that Kimbert will re-iterate) is to FIX the source of the data.
One common source of this problem is the dreaded cut/paste.
I know of several systems where if people type the data into the text fields in the web forms everything works fine.
If however they do a cut/paste from another document, typically MS-Word they get these 'screwed' up characters.
_________________
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 |
|
|
| kimbert |
| Posted: Tue Mar 01, 2011 4:54 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| it throws xml parsing error |
Please quote the full error. Error messages contain a *lot* of information about how to fix the problem. Look in Windows Event Viewer, or take a user trace, or use Google to find the message catalog ( search for the BIPxxxxE number ) |
|
| 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
|
|
|
|
