[FLEX-22169] Invalid "null" Number passed in web service calls.

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Invalid
• Affects Version/s: Adobe Flex SDK Previous
• Component/s: RPC: WebService
• Environment: Affected OS(s): All OS Platforms; Affected OS(s): All OS Platforms; Language Found: English
• Assignee: Adobe JIRA
• Reporter: Adobe JIRA
• Created: 25/Nov/09 01:02
• Updated: 15/Apr/11 14:57
• Resolved: 15/Dec/09 09:51

Description

Steps to reproduce:
1. Use wizard to create a Data/Service connection to the attached wsdl (any wsdl with a Number parameter passed will do).
2. Call the web service without inizialing the number passed.

Actual Results:
<SOAP-ENV:Body>
<tns:getNumber xmlns:tns="http://example.com/">
<tns:arg0>NaN</tns:arg0>
</tns:getNumber>
</SOAP-ENV:Body>
The web service call contains the string NaN where the wsdl states a numeric type (long in the example attached).

Expected Results:
<SOAP-ENV:Body>
<tns:getNumber xmlns:tns="http://example.com/">
<tns:arg0 xsi:nil="true"/>
</tns:getNumber>
</SOAP-ENV:Body>
Or
<SOAP-ENV:Body>
<tns:getNumber xmlns:tns="http://example.com/" />
</SOAP-ENV:Body>

The invalid number should be passed as null or omitted, so the wsdl call is valid. If you want the "NaN" behaviour be the default one, at least provide some way to state that all NaN numbers should be converted to null when sendind them in a web service.

Workaround (if any):
Create some wrapper on the server that translate the "NaN" strings in null objects without refusing the request.