locked
Problems with ArrayList deserialization migrating from WSE 2.0 SP3 to WSE 3.0 RRS feed

  • Question

  • I'm migrating my aplication from WSE 2.0 SP3 to WSE 3.0 and I'm having some problems with the ArrayList class deserialization.
    My web service extends from SoapService and has a web method that receives as a parameter an instance of a class called AdminMessage that contains an ArrayList type property called Parameters. When I call this web method with an instance of the AdminMessage with some strings inside the Parameters property I got an annoying result: WSE 3.0 deserialize the ArrayList into an array of XmlNode type.

    The soap envelop generated is this:
    <soap:Envelope xmlns:xop="http://www.w3.org/2004/08/xop/include" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
    <soap:Header />
    <soap:Body>
    <AdminMessage xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://tempuri.org/">
    <Parameters>
    <anyType xsi:type="xsd:string">PARAM 1</anyType>
    <anyType xsi:type="xsd:string">PARAM 2</anyType>
    </Parameters>
    <Results />
    </AdminMessage>
    </soap:Body>
    </soap:Envelope>

    I hope someone can help me. Thanks in advance.

    Wednesday, May 17, 2006 3:06 AM