| Author |
Message
|
| adubya |
 Posted: Sun Feb 24, 2013 1:07 am Post subject: |
 |
|
Partisan
Joined: 25 Aug 2011
Posts: 377
Location: GU12, UK
|
| alastair wrote: |
| Unescaping tags I have no problem with. Unescaping element values generates invalid XML. See my example above. |
When you serialize the content ready to output then the XMLNSC parser will re-escape the content.
The input XML was valid (escaped characters), the XMLNSC parser unescapes that content when parsing the document and presents the flow with the uescaped data. As above, when you then output that data (say to an MQOutput node) then the XMLNSC parser will re-escape the content. |
|
| Back to top |
|
 |
| alastair |
| Posted: Sun Feb 24, 2013 1:12 am Post subject: |
|
|
Novice
Joined: 08 Feb 2012
Posts: 18
Location: Sydney
|
| I hear what you're saying but that hasn't happened. As in my example the XML in the MQOutput node does not validate. I'll have a play around some more with some smaller examples to understand the behaviour of the parsing and serialising. |
|
| Back to top |
|
|
| adubya |
| Posted: Sun Feb 24, 2013 1:15 am Post subject: |
|
|
Partisan
Joined: 25 Aug 2011
Posts: 377
Location: GU12, UK
|
| alastair wrote: |
| I hear what you're saying but that hasn't happened. As in my example the XML in the MQOutput node does not validate. I'll have a play around some more with some smaller examples to understand the behaviour of the parsing and serialising. |
What error are you getting from the MQOutput node ? |
|
| Back to top |
|
|
| alastair |
| Posted: Sun Feb 24, 2013 1:20 am Post subject: |
|
|
Novice
Joined: 08 Feb 2012
Posts: 18
Location: Sydney
|
No error. Just getting invalid XML in the output.
This is not valid XML:
<Value>~!@#$%^&*()_+<,>.:;"'?/{[}]\|122ABCD 456789</Value> |
|
| Back to top |
|
|
| adubya |
| Posted: Sun Feb 24, 2013 1:26 am Post subject: |
|
|
Partisan
Joined: 25 Aug 2011
Posts: 377
Location: GU12, UK
|
Ah, OK. So that's the XML which ends up on the MQ queue ? Did you miss out the CDATA content in that example or doesn't it get output ?
Last edited by adubya on Sun Feb 24, 2013 1:31 am; edited 1 time in total |
|
| Back to top |
|
|
| alastair |
| Posted: Sun Feb 24, 2013 1:31 am Post subject: |
|
|
Novice
Joined: 08 Feb 2012
Posts: 18
Location: Sydney
|
| I have not forced the output to be CDATA using ESQL if that is what you mean. |
|
| Back to top |
|
|
| alastair |
| Posted: Sun Feb 24, 2013 2:21 am Post subject: |
|
|
Novice
Joined: 08 Feb 2012
Posts: 18
Location: Sydney
|
| I have a horrible feeling that RFHUTIL has been leading me on a wild goose chase. When I use it to put a test message with escaped chars and use it again to read it at the other end, the lengths are the same. But I have a feeling that RFHUTIL is rendering the content of the output for me. |
|
| Back to top |
|
|
| adubya |
| Posted: Sun Feb 24, 2013 2:23 am Post subject: |
|
|
Partisan
Joined: 25 Aug 2011
Posts: 377
Location: GU12, UK
|
| Ahaha! Switch to the "Both" option on the Data tab to see the hex/char representation of the message and see what things look like. |
|
| Back to top |
|
|
| alastair |
| Posted: Sun Feb 24, 2013 2:33 am Post subject: |
|
|
Novice
Joined: 08 Feb 2012
Posts: 18
Location: Sydney
|
Confirmed. RFHUTIL XML view should not be taken literally. If I switch to the "both" view the escaped characters are in plain view.
Kind thanks for helping with my problem @adubya! |
|
| Back to top |
|
|
|
|
