Forum Discussion

ahart's avatar
ahart
Occasional Contributor
11 years ago

Does Sourceforge accurately show the status of old bugs?

Because, this one seems to match exactly a problem that I am encountering (copied and pasted from Sourceforge)

493 schema compliance xsi:type="xs:string" None open 2009-09-29 2009-09-29 5

Which is that I am failing schema validation in SoapUi when I try to return a String in a list of anyType. If I edit the response and remove the xmlns declaration attributes for xs and xsi, it validates successfully.
  • redfish4ktc2's avatar
    redfish4ktc2
    Super Contributor
    Forget about this bug tracker, it is not used by SmartBear. You should post a message in the Soapui Bugs forum
  • ahart's avatar
    ahart
    Occasional Contributor
    This forum, right?

    Besides the sourceforge defect at http://sourceforge.net/p/soapui/bugs/493/ it appears like it has been reported a couple of times in this forum already:

    http://forum.soapui.org/viewtopic.php?t=7681

    A similar bug was reported fixed in 2009.

    The problem is occurring with the list of object inside the payload complex type:

             <xs:complexType name="payLoad">
    <xs:sequence>
    <xs:element minOccurs="0" name="responseInfo" type="tns:wsResponseInfo"/>
    <xs:element minOccurs="0" name="payLoadList">
    <xs:complexType>
    <xs:sequence>
    <xs:element form="qualified" maxOccurs="unbounded" minOccurs="0" name="payLoadObject" type="xs:anyType"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    </xs:sequence>
    </xs:complexType>


    There is no problem if the list contains one of the complex types defined in my target namespace. The problem occurs when I try to return a String.

    In the response, it looks like this:

    <ns2:payLoadObject xsi:type="xs:string" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Test of the WS-VTA Web Service</ns2:payLoadObject>


    and this fails schema validation with the error: "Invalid xsi:type qname 'xs:string' in element payLoadList". If I edit the response to delete the xs and xsi namespace declaration attributes from the payLoadList element, it succeeds.