Re: Custom Pipeline Component Adding Rootnode and NameSpace

I think your idea of using an Xml.XmlDocument as the receive type would most likely provide the most flexibility.  Then on the response you could see what the root node is and handle it appropriately.