Adobe FLEX 2-MIGRATING APPLICATIONS TO FLEX 2 Manual page 96

Migrating applications to flex 2
Table of Contents

Advertisement

mx.servicetags.RemoteObject
The RemoteObject class was moved to mx.rpc.remoting.RemoteObject. It now extends the
mx.rpc.AbstractService class.
The following table describes changes to the RemoteObject class:
Member
encoding
endpoint
named
protocol
source
type
All RemoteObject sources need destination entries in the flex-services.xml file. You should
now name every service and not use the actual source class as the name. All definitions of
named RemoteObjects must be moved into the flex-services.xml file.
mx.servicetags.WebService
The following table describes changes to the WebService class:
Member
protocol
serviceName
The WebService class has the following changes:
The WebService class was moved to mx.rpc.soap.WebService. It now extends the
mx.rpc.AbstractService class.
You must move the definitions of named services to the flex-services.xml file. The
unnamed whitelist must be updated in the defaultHttp destination.
96
Flex Classes
Change description
Removed.
Was removed. Channels defined in the flex-services.xml
file replace the need for this property.
Has been added again to allow clients to use this tag
without the configuration file at compile time.
Removed. Use the
destination
Removed. Channels defined in the flex-services.xml file
replace the need for this property.
Removed. Use the
destination
Removed. This is now controlled in the service definition in
the flex-services.xml file. You set it with the
Change description
Deprecated. Use the
compatibility, the default value of the
is
.
defaultHttps
Deprecated. Use the
property.
property.
property. For backward
destination
destination
property.
destination
tag.
<source>
property

Advertisement

Table of Contents
loading

This manual is also suitable for:

Flex 2

Table of Contents