elguapo,

Since interoperability is important in your case (your #2 requirement), it
is not suggested that you send any data types that are specific to .NET.  If
you plan on sending the XML Document as an XmlNode, make sure to have it
properly serialized as an XML element.

I have researched doing this and came up with 2 ways to pass an XML
Document:
1. By a string type element
2. By using the xsd:any

I have tested both solutions and they both work, however it's up to your
requirements on which you would like to do.  I find that #1 is the easiest
solution to implement, but because the XML document is wrapped into a string
type, you won't be able to directly manipulate the XML (without having to
load it into another XmlDocument at least).

$2 solution is a little more difficult to implement (in Java at least, .NET
is pretty simple), but this does have the benefit of having your XML
document as part of the overall XML structure being passed by the web
service.

Hope this helps.

Eric

Hi elguapo,
       I am currently implementing a similar project. We adopted the
approach of defining our types as xsd schema, and xml serialization. We used
the xsd tool to generate class definitions of the classes that we will be
sending as paramters and return types.

This was then integrated into the WSDL document. The proxy classes whent hey
reference the web service are provided with class definitions they can use.

In conjunction with this we payed close attention to the WS-Profile document
produced for Interoperability available at msdn.

Hope this helps

Lenin