Menu
We have produced a web service in VB.NET against a WSDL file provided to us by our client.
In testing, our client has raised an issue complaining that the XML produced by our web service uses 'true' and 'false' for boolean values, not '1' and '0'. Furthermore, they are suggesting that our implementation is 'broken' because of this.
I was under the impression that 'true/false' and '1/0' in this context were interchangeable?
Either way, all of the XML serialisation is being handled by the .NET framework, not our code - so I assume I have little chance of changing it anyway?!
Can anyone point me to some documentation which either backs up my story or proves me wrong? If I am wrong, does anyone know how I might be able to alter this behaviour?
Thanks in advance...
560
The encoding style for a SOAP message is set via the SOAP-ENV:encodingStyle attribute. Latest SOAP specification adopts all the built-in types defined by XML Schema. Still, SOAP maintains its own convention for defining constructs not standardized by XML Schema, such as arrays and references.
SOAP defines a binding to the HTTP protocol. This binding describes the relationship between parts of the SOAP request message and various HTTP headers. All SOAP requests use the HTTP POST method and specify at least three HTTP headers: Content-Type, Content-Length, and a custom header SOAPAction.
A SOAP message is encoded as an XML document, consisting of an <Envelope> element, which contains an optional <Header> element, and a mandatory <Body> element. The <Fault> element, contained in <Body> , is used for reporting errors.
The SOAP Envelope Element This element defines the XML document as a SOAP message.
From the SOAP spec: 'the boolean lexical forms "1" and "true" are interchangeable.'
Not much more to say, really.
93
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
