Hello, At work we're a client to a web service that allows either or both of two search criteria for a "Get" SOAP request input that can cause inconsistent results when both values are supplied. They are using an xsd:sequence with a minOccurs="0" for both, although supplying neither nor both does not make sense for this particular operation. I am about to recommend that they switch to xsd:choice, which could be used to enforce exactly one of the two input options be used, but first wanted to check whether there's anything wrong with usage of xsd:choice within WSDLs in particular.
For example, imagine a web service FindConvenienceStores that allows for searching by ZIP code and by State (with an xsd:sequence allowing that)-- it is not useful to supply both values, and undefined results can happen when you supply both a ZIP code and a state that that ZIP code is not in. I'd like to recommend they switch to xsd:choice unless I'm missing something here. Thanks, Glen -- View this message in context: http://www.nabble.com/Anything-wrong-with-xsd%3Achoice-in-WSDLs--tp23562197p23562197.html Sent from the cxf-user mailing list archive at Nabble.com.
