Schema validation on WSDL for Inbound Siebel Web Services
All,
I would appreciate some feedback or suggestions on the following:
Our middleware team would like to implement schema validation when wrapping Siebel Web Services, but the data contained in the WSDL make this difficult at the moment (i.e. it is incorrect).
By default Siebel sets Integration Object Fields as required if the corresponding Field is Required on the Business Component. This in turn makes the element mandatory according to the WSDL as follows:
...
<xsd:element name="ContactFirstName" maxOccurs="1" minOccurs="1" type="xsd:string" />
...
If this is a query Web Service it does (normally) not make sense that the Contact First Name should be mandatory. However, I am unsure how this should be adressed?
0