| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Which XML parser does MQSI use????? |
« View previous topic :: View next topic » |
| Author |
Message
|
| kiran26 |
 Posted: Wed Aug 07, 2002 2:34 pm Post subject: Which XML parser does MQSI use????? |
 |
|
Acolyte
Joined: 06 Feb 2002
Posts: 69
|
Hi all,
My question is, which XML parser does the MQSI V2.1 uses internally for parsing the in coming XML messages.
Thanks
kiran |
|
| Back to top |
|
 |
| kirani |
| Posted: Wed Aug 07, 2002 3:38 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
From IBM documentation ...
| Quote: |
MQSeries Integrator V2 contains a Generic XML parser that will parse any well-formed XML message and will create output messages with well-formed XML tags. This parser uses the domain name of “XML”. The generic parser is built using a level of the XML4C parser that does not support XML namespaces directly. It will treat a qualified name as a simple name that happens to have a colon embedded in the name. Therefore, messages with qualified tag names can be parsed or created. There is no checking performed regarding the proper use of XML namespaces within the documents.
|
Here is more info on XML4C ...
| Quote: |
IBM's XML for C++ parser (XML4C) is based on Apache's Xerces-C XML parser, which is a validating XML parser written in a portable subset of C++. XML4C integrates the Xerces-C parser with IBM's International Components for Unicode (ICU) and extends the number of encodings supported to over 150.
|
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| MVO |
| Posted: Mon Aug 12, 2002 7:06 am Post subject: |
|
|
Centurion
Joined: 09 Sep 2001
Posts: 131
|
Hi,
There is a BIG problem with ther Xerces XML parser: it converts all <CR> to <LF>.
This is against the principle of leaving the message body intact !!!
IBM gave me a workraround - reset the message content to BLOB before it leaves WMQI and scan through the message to replace any occurence of <LF> with <CR>. Second violation !!! What if you need both <CR> and <LF> at the destination end ? Now we're into another workaround, replacing <LF><LF> with <CR><LF> ???
I really need help for this !!!
MVO |
|
| Back to top |
|
|
| mpuetz |
| Posted: Mon Aug 12, 2002 12:23 pm Post subject: |
|
|
Centurion
Joined: 05 Jul 2001
Posts: 149
Location: IBM/Central WebSphere Services
|
Hi,
the conversion of <CR> or <CR><LF> is required according
to the XML 1.0 specification chapter 2.11, hence the Xerces
parser is doing this correctly (I only learned that recently that as well).
Thus XML-applikations which actually require <CR> and
parse it are not XML-conformant.
_________________
Mathias Puetz
IBM/Central WebSphere Services
WebSphere Business Integration Specialist |
|
| Back to top |
|
|
| wolstek |
| Posted: Thu Aug 22, 2002 7:17 am Post subject: |
|
|
Acolyte
Joined: 25 Jun 2001
Posts: 52
Location: Bristol, UK
|
| We experienced similar issues regarding CRLF. Apparently the correct way to deal with this in pure XML is to BASE64 encode the data between XML tags that are not to be changed by XML parsers. This is fine if all you want to do is pass the data string through without looking at it and without having it parsed. If you want to look at the data then you might have to extract into a separate XML tag upstream of the XML parser getting its teeth into it. |
|
| 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
|
|
|
|
