Incorrect SOAP response message generated when ElementFormDefault="unqualified" - Known Error

Incorrect SOAP response message generated when ElementFormDefault="unqualified" Description An incorrect SOAP response message is generated when ElementFormDefault="unqualified". This is seen when the SOAP response does not state which table the record should be inserted into.

For instance, a SOAP response should contain a value such as this:

005ae3231b203000f1129141be0713cf..... omitted .... 216

However, the following is seen:

005ae3231b203000f1129141be0713cf..... omitted .... 216 Steps to Reproduce Make sure glide.wsdl.schema.UnqualifiedElementFormDefault=true in Web Services Properties .

Use SOAP-UI to invoke getKeys from incident.do?WSDL .

You would get following soap response:

http://schemas.xmlsoap.org/soap/envelope/" ; xmlns:xsd=" http://www.w3.org/2001/XMLSchema" ; xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance"> ; 005ae3231b203000f1129141be0713cf..... omitted .... 216

The problem is that getKeysResponse namespace is incorrectly omitted.

What should be done is the global element getKeysResponse should be namespace-qualified and the local namespace should not be qualified since WSDL document defined ElementFormDefault="unqualified" . http://www.w3.org/TR/xmlschema-0/#NS

This is what it should look like:

http://schemas.xmlsoap.org/soap/envelope/" ; xmlns:xsd=" http://www.w3.org/2001/XMLSchema" ; xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance"> ; http://www.service-now.com/incident> ; 005ae3231b203000f1129141be0713cf..... omitted .... 216

Workaround Set the property glide.wsdl.schema.UnqualifiedElementFormDefault to false .