Migrating Webservice Components - Adobe FLEX 2-MIGRATING APPLICATIONS TO FLEX 2 Manual

Migrating WebService components

The default value of the
configured in the
<proxy-service>
includes by reference. They were previously described in the
of the flex-config.xml file.
To bind service results in Flex 2, you use the
binding source, as the following example shows:
<mx:Text text="{tempService.getTemp.lastResult}"/>
In Flex 1.5, the
result
Unnamed WebService
This section describes how to migrate unnamed WebService tags from Flex 1.5 to Flex 2.
For unnamed WebServices tags that set
changes. These tags already ignore all server side configuration.
Flex 1.5 syntax
In Flex 1.5, you added an unnamed whitelist entry to the
the configuration file.
MXML tag:
<mx:WebService id="MyService" wsdl="http://myServer.com/services/my.wsdl"/>
flex-config.xml file:
<web-service-proxy>
<whitelist>
<unnamed>
<url>http://myServer.com/services/*</url>
</unnamed>
</whitelist>
</web-service-proxy>
Flex 2 syntax
In Flex 2, the MXML tag syntax for an unnamed WebService is almost the same, but you
must also set the value of the
property that was available in Flex 1.5; the channel defines the protocol. In the
protocol
configuration file, you must specify a channel and an adapter that matches the value of the
attribute.
wsdl
property is
useProxy
section of the services-config.xml file or a file that it
property was the binding source.
useProxy="false"
property to
useProxy
. The WebService tags are now
false
<web-service-proxy>
property of the service as the
lastResult
, you are not required to make any
<web-service-proxy>
. Flex 2 does not support the
true
Migrating WebService components
section
section of
143