2.0.2 Pro: choice issue with Form mode
Hi,
We have a problem with SoapUI 2.0.2 Pro when creating a request in form mode and the request contains a between two elements.
I created a small WSDL to illustrate the issue (full WSDL attached).
It looks like this:
or in xml:
To see the problem, create a request with it in form mode, switch to XML mode and you'll get:
This is clearly wrong. There should only be one tag and no.
It doesn't even validate:
Note that if you fix it in XML, switch to form mode and back, it's gone wrong again. Therefore, the only solution right now is to set the default edit mode to be XML but I have to switch to form mode for every other request in the project.
We have a problem with SoapUI 2.0.2 Pro when creating a request in form mode and the request contains a
I created a small WSDL to illustrate the issue (full WSDL attached).
It looks like this:
or in xml:
<xsd:element name="NewOperation">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="a" type="xsd:string" />
<xsd:choice>
<xsd:element name="b" type="xsd:string"></xsd:element>
<xsd:element name="c" type="xsd:string"></xsd:element>
</xsd:choice>
<xsd:element name="d" type="xsd:string"></xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
To see the problem, create a request with it in form mode, switch to XML mode and you'll get:
<soapenv:Body>
<soap:NewOperation>
<a>sdfsqdf</a>
<!--You have a CHOICE of the next 2 items at this level-->
<b>?<b>bbbbbbb</b></b>
<c>?</c>
<d>jkhkjh</d>
</soap:NewOperation>
</soapenv:Body>
This is clearly wrong. There should only be one tag and no
It doesn't even validate:
line 7: Element not allowed: b in element b
line 8: Expected element 'd' instead of 'c' here in element NewOperation@http://www.vivansa.com/soapuitest/
Note that if you fix it in XML, switch to form mode and back, it's gone wrong again. Therefore, the only solution right now is to set the default edit mode to be XML but I have to switch to form mode for every other request in the project.
