| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Unable to Process URL Encoded XML Elements in a Compute Node |
« View previous topic :: View next topic » |
| Author |
Message
|
| albitkw |
 Posted: Thu May 05, 2005 5:49 am Post subject: Unable to Process URL Encoded XML Elements in a Compute Node |
 |
|
Novice
Joined: 02 May 2005
Posts: 15
Location: Pittsburgh, PA
|
An XML message is received with a <DATA> element containing an URL encoded string that substitutes less than ("<"), greater than (">"), and slach ("/") characters with "%3C", "%3E", and "%2F" respectively (see example below)
The MRM parser accepts the message in the INPUT node. In a following compute node, the encoded string is visable in InputRoot.MRM.Data, but the value copied from InputRoot.MRM.Data to OutputRoot.MRM.Data becomes NULL, and attempts to copy InputRoot.MRM.Data to a local character variable also produces NULL.
Other encoded characters that are not part XML tag syntax do not cause these issues. It seems that ESQL has difficulty only with these three characters.
Is there a way in ESQL to decode the encoded characters in the <DATA> tag (like the .Net URLDECODE function, which can decode %3C, %3E, and %2F properly)? I would at least like to get to the point where InputRoot.MRM.Data can be copied to OutputRoot.MRM.Data.
It would be really great if the message could be reparsed so that the encoded tags become part of the message tree.
Before encoding:
<DATA><ext_sec_id>1202002050</ext_sec_id><DATA>
encoded as: 
<DATA>%3Cext_sec_id%3E1202002050%3C%2Fext_sec_id%3E<DATA> |
|
| Back to top |
|
 |
| malammik |
| Posted: Thu May 05, 2005 1:20 pm Post subject: |
|
|
Partisan
Joined: 27 Jan 2005
Posts: 397
Location: Philadelphia, PA
|
|
| 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
|
|
|
|
