SET OutputRoot.XMLNSC.(XMLNSC.XmlDeclaration) = '';
SET OutputRoot.XMLNSC.(XMLNSC.XmlDeclaration)*.(XMLNSC.Attribute)Version = '1.0';
SET OutputRoot.XMLNSC.(XMLNSC.XmlDeclaration)*.(XMLNSC.Attribute)Encoding = 'UTF-8';
SET OutputRoot.XMLNSC.(XMLNSC.XmlDeclaration)*.(XMLNSC.Attribute)standalone = 'no';
You will notice that, by default, XMLNSC discards them when parsing. But you can still put them into the message tree using ESQL. And you can also politely ask XMLNSC not to discard them when parsing. So...
1. Create a minimal document containing your processing instruction
2. Create a tiny message flow that parses that document. Make sure that you have enabled the special setting that preserves processing instructions for XMLNSC!
3. Add a Trace node after the input node and set the pattern to ${Root}
4. Examine the output of the Trace node. It will tell you exactly what the message tree needs to look like if you want to generate that document.
5. In your real message flow, add a single line of ESQL to create your processing instruction.
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