[Mono-list] Nullable types in web services
Atsushi Eno
atsushi at ximian.com
Wed Feb 14 04:26:34 EST 2007
Hi,
If the exact reported bug still happens then please reopen. Otherwise
filing a new bug is better, as your issue is likely related to different
issue then.
Atsushi Eno
Oleg Deribas wrote:
> Hello,
>
> Andrés G. Aragoneses [ knocte ] said the following on 18.01.2007 22:21:
>
>> http://bugzilla.ximian.com/show_bug.cgi?id=80551
>
> I've tried to get nullable integer from web service using latest mono
> 1.2.3 and it still doesn't work. It seems there is another problem.
>
> For testing I use simple method:
>
> int? GetNull()
> {
> return null;
> }
>
> Here is fragment of WSDL I've got from IIS:
>
> <s:element name="GetNullResponse">
> <s:complexType>
> <s:sequence>
> <s:element minOccurs="1" maxOccurs="1" name="GetNullResult"
> nillable="true" type="s:int" />
> </s:sequence>
> </s:complexType>
> </s:element>
>
> and this is what I've got from XSP2:
>
> <xs:element name="GetNullResponse">
> <xs:complexType>
> <xs:sequence>
> <xs:element minOccurs="1" maxOccurs="1" name="GetNullResult"
> type="xs:int" />
> </xs:sequence>
> </xs:complexType>
> </xs:element>
>
> The difference is that mono doesn't set nillable="true" attribute.
> Should I reopen bug 80551 or it is another bug and should be filed
> separately?
>
More information about the Mono-list
mailing list