XMLNSC remembers that the data came from a CData section, and it will generate a CData section in the output. So you must have done something to the message tree after parsing. Did you copy it to the Environment or LocalEnvironment, perhaps?
I suggest that you put in at least two Trace nodes : the first one should go immediately after the CREATE...PARSE statement. You should see that the parser-specific field type is set to 'XMLNSC.CDataField' on element 'a'. Then put another Trace node just before the ASBITSTREAM. You will probably find that the XMLNSC.CDataField on element 'a' has disappeared because your flow has copied the tree incorrectly.
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