Posted: Mon Apr 20, 2020 9:39 am Post subject: Allowing missing elements in request to SOAP Input Node?
Centurion
Joined: 23 Sep 2010 Posts: 130
Hello all :
Have a message flow in IIB9.0.0.1 that using a SOAP Input. Two clients call this SOAP web service.
One of the clients is not sending a field that is defined in the message model, so w are getting a parsing error. They are not sending this because the value would always be false in that system and we didn't want (or quite frankly - didn't think) to modify that system to send the value in.
So I was hoping that in the message set when defining that element, I could make it nillable or set a default string of "false" That does not appear to be working. The default message domain is SOAP with supported message domain XMLNSC.
Are my only two options (assuming keeping the SOAP Input Node) is to either have the client send the value or leave validation off?
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
If the field is optional then you can specify it with minOccurs=0 in the WSDL. That's not the same as a field which must be present but can contain a null. _________________ Honesty is the best policy.
Insanity is the best defence.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum