Custom pipeline - problem and solution

Developed a custom pipeline for an application,
1 - The pipeline received a binary file from an FTP receive location
2 - The custom pipeline - the disassemble stage transformed the binary file into an xml message to be passed to the messaging engine and so delivered to the processing orchestration
3 - A map in my orchestration didnt recognize the message! despite the fact that I was able to examine the passed message using HAT
4 - Earlier while developing the pipeline I constructed the message as:
<Root>
<Field1>val</Field1>
<Field2>val</Field2>
<Field3>val</Field3>
<Field4>val</Field4>
</Root>
The map didnt recognize the message because the namespace of the message was missing
5 - To solve the problem constructed the message as
<ns0:Root xmlns:ns0="http://MyApp.Msgs">
<Field1>val</Field1>
<Field2>val</Field2>
<Field3>val</Field3>
<Field4>val</Field4>
</ns0:Root>