SoapUI schema interpretation bug

[SBM]

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.

[SmartBear_Suppo]

Hi,

this looks like one of the known limitations with the form editor, ie a choice of anonymous complex types. Thanks for reporting though, I'll put it in our backlog for fixing.

regards!

/Ole
eviware.com

[sebisteiner]

Hi

What is the status of this bug?

I have the same issue with soapUI Pro 4.0.1

Greetings,
Sebi

[SmartBear_Suppo]

Hi Sebi,

this is still unresolved - I'm very sorry to keep you waiting.

I'll move this to the Pro Bugs Forum Board - since it is soapUI Pro related..

regards!

/Ole
SmartBear Software