XmlSerializatio n serializing with xsi:type specified

[pfrisbie]

I am developing a Web Services interface with C# and our partner is
using Java (Axis 1.1). They require me to include xsi:types in the
SOAP Messages I send them. For example:

<Partner xmlns="urn:part ner.xxxxx.com">
<RequestID>23 9</RequestID>
<TimeStamp>20 06-03-06T17:10:51.466 2331-06:00</TimeStamp>
<Subject xmlns:ns1="urn: partnermapping. xxxxxx.com"
xsi:type="ns1:P artnerMapping">
<AccountID>9840 1</AccountID>
</Subject>
</Partner>

Is this possible with XmlSerializatio n? I searched all over and cannot
find any examples of this. How do I specify it using .Net
XmlSerializatio n?

Thanks,

pfrisbie

[6kjfsyg02]

pf******@hotmai l.com wrote:

I am developing a Web Services interface with C# and our partner is
using Java (Axis 1.1). They require me to include xsi:types in the
SOAP Messages I send them. For example:
I had the opposite problem. The web services were not sending me the
xsi:type that I required to deserialize properly a certain element.

What i did was a SoapExtension that searched for the element and if the
xsi:type was not present it would add it manually manipulating the
XmlDocument.
pfrisbie

--
David Mediavilla

[pfrisbie]

David, you are right, a SOAP Extension would work. I'm wondering if
your WebService required an xsi:type then that suggests that
XmlSerializatio n is aware of xsi:types so it should be able to
deserialize them as well. Is there are attribute or something in your
classes that looks like it sets the xsi:type? Thanks -- Pat.

[pfrisbie]

I meant to say: "... that suggests that XmlSerializatio n is aware of
xsi:types so it should be able to SERIALIZE them as well. ..." -- Pat

[6kjfsyg02]

My code required an xsi:type because that element was declared as:

[System.Xml.Seri alization.XmlEl ementAttribute( Namespace="http ://the.namespace/")]
public object theUnknownEleme nt;

It was an object because each service provided a different type. I have
several SoapHttpClientP rotocol that deal with each service:

[System.Xml.Seri alization.XmlIn clude( typeof( OneSpecificType ))]
public class GeneratedStub:
System.Web.Serv ices.Protocols. SoapHttpClientP rotocol
{...}

The services did not provide an xsi:type because they provided always
the same type. It was me who had to be flexible.

My testing Web Service also had [XmlInclude( typeof(
OneSpecificType ))].

You could also examine their WSDL and hack it to turn Subject into a
anyType or Choice. Look also abstract elements (
http://www.w3.org/TR/xmlschema-0/#abstract ).
Generate code from the hacked WSDL and compare with what you have.
If you don't have Java's WSDL, try to generate one from your client.

--
David Mediavilla