You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The WSDL schema that is generated for fields or properties with the [XmlAttribute] attribute is not correct. It differs from the WSDL that is generated by a ASP.NET ASMX Web Service. Let's take a look at the following class:
However the WSDL that is generated by ASMX Web Services in .NET Framework is different. It adds the use="required" attribute for value types (such as int), to indicate that they are required. The required attribute is added for all value types, except if the class defines a ShouldSerialize*() method, which makes the type optional again.
This is the how the generated WSDL should actually look:
If a member has been annotated with the [XmlAttribute] attribute, and it
is a value type, such as int, it will get the use="required" attribute.
However if it has a ShouldSerialize*() method, then it is considered
optional and the use="required" attribute is not added.
Added a new test to verify this behavior.
FixesDigDes#1006
The WSDL schema that is generated for fields or properties with the
[XmlAttribute]
attribute is not correct. It differs from the WSDL that is generated by a ASP.NET ASMX Web Service. Let's take a look at the following class:SoapCore will generate a WSDL, such as the following:
However the WSDL that is generated by ASMX Web Services in .NET Framework is different. It adds the use="required" attribute for value types (such as int), to indicate that they are required. The required attribute is added for all value types, except if the class defines a
ShouldSerialize*()
method, which makes the type optional again.This is the how the generated WSDL should actually look:
This applies to the current version v1.1.0.42.
The text was updated successfully, but these errors were encountered: