14 years ago
SoapUI schema interpretation bug
I've got some schema definitions making use of "choice" between two anonymous sequences.
Example:
<xs:complexType name="SomeComplexType">
<xs:choice>
<xs:sequence>
<xs:element ref="tns:oneComplexType"/>
<xs:element ref="tns:anotherComplexType"/>
<xs:element ref="tns:aThirdComplexType"/>
</xs:sequence>
<xs:sequence>
<xs:element ref="tns:theFourthComplexType"/>
<xs:element ref="tns:theFifthComplexType"/>
<xs:element ref="tns:theSixthComplexType"/>
</xs:sequence>
</xs:choice>
</xs:complexType>
SoapUI form view seem unable to handle this. When I switch from XML view to Form view and back - without altering anything - a substansial part of the XML is gone. It seems to me, soapui misinterpretes the choice.
I've attached a SoapUI project that exemplifies this. It's the only request in the only testcase in the only testsuite. Just open it in XML view. Then switch to Form View and back, and a lot of the XML is gone.
Example:
<xs:complexType name="SomeComplexType">
<xs:choice>
<xs:sequence>
<xs:element ref="tns:oneComplexType"/>
<xs:element ref="tns:anotherComplexType"/>
<xs:element ref="tns:aThirdComplexType"/>
</xs:sequence>
<xs:sequence>
<xs:element ref="tns:theFourthComplexType"/>
<xs:element ref="tns:theFifthComplexType"/>
<xs:element ref="tns:theSixthComplexType"/>
</xs:sequence>
</xs:choice>
</xs:complexType>
SoapUI form view seem unable to handle this. When I switch from XML view to Form view and back - without altering anything - a substansial part of the XML is gone. It seems to me, soapui misinterpretes the choice.
I've attached a SoapUI project that exemplifies this. It's the only request in the only testcase in the only testsuite. Just open it in XML view. Then switch to Form View and back, and a lot of the XML is gone.