Are you *positive* that the "." and the space don't exist in the input message?
And did not exist as strange, wayward, undisplayed, unescaped hex in the original message? Where "." and space are the broker's attempt to mangle them into a form that parses?
Or the QM's attempt to convert them into UTF-16....
Nobody told me about checking the 'Retain Mixed Content' checkbox on the Parser Options of the input node
True. But somebody did suggest that you insert a Trace node into your message flow. That would have shown you very clearly that the mixed content was not even in the message tree.
At risk of repeating myself, the best way to diagnose parser problems is:
- disconnect debugger
- Insert trace node(s)
- take a user trace
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