| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Badly formed xml |
« View previous topic :: View next topic » |
| Author |
Message
|
| jeeth_m |
 Posted: Tue Dec 28, 2004 5:20 pm Post subject: Badly formed xml |
 |
|
Voyager
Joined: 21 Jan 2002
Posts: 93
|
Hi,
Messages are failing in the input Queue of the message flow with
Error message "badly formed XML".
It says Causes of failure is x'1A' as invalid data.
If these chars are with in CDATA xml parser is not supposed to parse them rite...
any idea why its still failing?
Jeeth |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Dec 28, 2004 5:43 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
CDATA sections are not completely isolated from the parsing requirements.
So, no, the parser may not ignore them.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| jeeth_m |
| Posted: Tue Dec 28, 2004 8:25 pm Post subject: |
|
|
Voyager
Joined: 21 Jan 2002
Posts: 93
|
can you give me more details about it.
I do not see any where about this in docs.
Jeeth |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Dec 29, 2004 4:17 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
It's not in the WBIMB docs. The IBM docs assume you understand XML.
It's somewhere in the XML specification for CDATA. I don't remember off the top of my head where, but you should not have lots of problems finding it.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| sieijish |
| Posted: Fri Dec 31, 2004 3:47 am Post subject: |
|
|
Acolyte
Joined: 29 Nov 2004
Posts: 67
Location: London
|
Hex '1A' is the EOF character (Ctr Z) and thats breaking the parser.
CDATA section is just an easy way of including text that has lots of characters which need escaping (like < and &). So when people say CDATA section are not parsed, it simply means that the content is not parsed in the context of 'XML'. ie, if the text <p> appears in a CDATA section, it is not considered as an xml element but as simple text. |
|
| Back to top |
|
|
| jeeth_m |
| Posted: Fri Dec 31, 2004 8:28 am Post subject: |
|
|
Voyager
Joined: 21 Jan 2002
Posts: 93
|
Here is the explanation i found in some IBM site.
Thanks all for your help.
Jeeth
The interpretation that text/bytes within CDATA would not be changed
is incorrect. In section 2.7 of the XML specification, the following
is stated :
'CDATA sections may occur anywhere character data may occur; they
are used to escape blocks of text containing characters which
would otherwise be recognized as markup.'
So from the above description, CDATA tags are used to preserve text
that could be regarded as markup. In section 2.7 of the XML
specification, the term markup is defined as :
'The definition of markup is start tags, end tags, empty element
tags, entity references, character references, comments, CDATA
section delimiters, document type declarations, processing
instructions, XML declarations, text declarations and white space.'
As can be seen from the definition above, carriage return characters
do not fall into the category of 'markup' and therefore should not
be preserved within CDATA.
Just like Carriage Return , x1A(Substitute) and x11(DC1) donot come under markup.
Hence the message failed. |
|
| 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
|
|
|
|
