| Author |
Message
|
| eugene |
 Posted: Tue Jun 01, 2010 11:41 am Post subject: 0x1a issue |
 |
|
Novice
Joined: 02 Mar 2010
Posts: 18
|
Hello to everyone,
Here is my simple question and sorry if it is obvious to some of you here - it is not so obvious to me.
We have an application that generates some types of messages - XML. Some of these messages have a certain field that once "touched" by the XMLNSC parser brake immediately.  This is a damn important field - it a digital signature or something like this -sorry but no access to the generating code. The error in debug is "Parsing Errors have occurred" and in logs it says something about the "0x1a". If it is important could post the exact error message.
Now, I have lost the entire evening looking for something that makes sense (girlfriend really mad right now  ) , all I could find is that the "ox1a" is a special character and that it can not be contained in XML at all. Does that mean that WMB can work with this kind of characters?
Also the encoding anywhere you can think is set to 1208.
Any hit or suggestion is appreciated. thx a lot!
Eugene. |
|
| Back to top |
|
 |
| mgk |
| Posted: Tue Jun 01, 2010 12:06 pm Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
| Quote: |
| If it is important could post the exact error message |
Yes it is important, so please post the full message. Also take a user trace and have a look at that as well...
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Jun 01, 2010 12:32 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
XML is not guaranteed to carry all byte data without any change - XML is defined as holding character data.
If 0x01 is an illegal character in XML, then no conforming XML parser will be able to work with it without either throwing an exception or replacing the illegal character with a legal substitution character.
Broker generally replaces bad characters with substitution characters, in order to allow you to process otherwise badly formed documents as much as possible.
But to be very clear here - it is very much the fault of whoever is GENERATING the XML document that you are unable to process it without mangling it. If 0x01 is an illegal XML character - then they are producing an illegal XML Document.
Tell them to base64 encode the digital signature and stop trying to treat XML as anything other than a character stream rather than a general purpose bytestream.
And post the full exception and take a user trace at debug level and examine what it says! |
|
| Back to top |
|
|
| eugene |
| Posted: Tue Jun 01, 2010 10:04 pm Post subject: |
|
|
Novice
Joined: 02 Mar 2010
Posts: 18
|
Well, I have asked them to generate a few other messages and now the error in logs is : "An invalid XML character (Unicode: 0xc) was found in the element content of the document. occurred on line 1 column 246 when parsing element ''/Root/XMLNSC/REQUEST/HEADER/SIGNATURE''. Internal error codes are '1502' and '2'." Is that of any help?
Now it's different XML Element - 0xc.
@mqjeff - totally agree that IT COULD be their error. Still I do not what to be part of the "third envelope" if you know I mean. And if you don't I will explain.  |
|
| Back to top |
|
|
| eugene |
| Posted: Tue Jun 01, 2010 11:12 pm Post subject: |
|
|
Novice
Joined: 02 Mar 2010
Posts: 18
|
| It seems that indeed we got messages that are not part of the XML specification. All they have to do know is base64 encode the signature and things should work... Hope that the next message of mine is going to be a big thx for the help. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jun 02, 2010 9:55 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Top tip in situations like this - take the offending message and try to display it with XMLSpy or similar. If that chokes on the XML as well, it's clearly a malformed document and a problem with the sender.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
