a problem with this and to make sure this is not a bug. When calling a
WebService from MXML, arguments that are empty are not sent at all,
which can cause problems if your WS requires they be present.
For example, in my MXML I had bound the text properties of a couple of
input fields as the arguments in my call.
<mx:WebService id="ws_search"
wsdl="http://server/Webservices/PseSearchWS.asmx?WSDL">
<mx:operation name="PseSearch" showBusyCursor="true">
<mx:request xmlns="">
<clientNm>
{client.text}
</clientNm>
<planNm>
{plan.text}
</planNm>
<RelationshipMgrNm>
{rm.text}
</RelationshipMgrNm>
<maxResults>
50
</maxResults>
</mx:request>
</mx:operation>
</mx:WebService>
If any of those fields were left blank, however, those nodes were not
sent in the request, which caused an error in the WS. This did not
happen in Beta 2.
The behavior is different though if you make the call from AS (using
mx.rpc.soap.WebService). mx.rpc.soap.WebService performs what I would
consider the 'correct' handling of this situation and sends empty
nodes: <clientNm />, <planNm />, etc.
Thoughts?
--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
SPONSORED LINKS
| Web site design development | Computer software development | Software design and development |
| Macromedia flex | Software development best practice |
YAHOO! GROUPS LINKS
- Visit your group "flexcoders" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
