MACROMEDIA FLEX 2-MIGRATING APPLICATIONS TO FLEX 2 Manuel d'utilisateur Page 136
- Page / 184
- Table des matières
- MARQUE LIVRES
Noté. / 5. Basé sur avis des utilisateurs
136 Data Services
Flex 2 separates the definitions of services into a new file, services-config.xml. This file
contains definitions of the services and security constraints that were previously in the flex-
config.xml file. Optionally, it can include other configuration files by reference. The services-
config.xml file is located in the flex_deploy_dir/flex/WEB-INF/flex directory of a web
application in which you are using Flex Data Services. If you use the command-line compiler,
you must point to this file with the -services option.
The underlying architecture for communicating with the server for each type of service is
based on a new messaging framework in Flex 2. As a result, you use message channels to
communicate with the service. You configure channels in the services-config.xml file. The
new new messaging framework uses channels to connect clients to endpoints; requests are
made by sending messages over channels to endpoints of a message broker that directs the
messages to the correct service.
For information about the client-side configuration of RPC components, see Chapter 45,
“Using RPC Components,” in the Flex 2 Developer’s Guide. For information about the server-
side configuration of RPC service destinations, see Chapter 46, “Configuring RPC Services”
in the Flex 2 Developer’s Guide.
Proxy use policy
In Flex 1.5, there was as setting that let you override the proxy. This was the <proxy-use-
policy>
setting in the flex-config.xml file. If you set it to client, Flex checked the value of
the
useProxy attribute on the service tag. The default was to use the proxy. If you set it to
always, Flex used the proxy regardless of the value of the useProxy attribute. If you set it to
never, Flex did not use the proxy regardless of the value of the useProxy attribute.
The
<proxy-use-policy>client</proxy-use-policy> setting does not exist in Flex 2.
Flex behaves as if the value is
client, which means that Flex checks the value of the
useProxy attribute on the service tag. The default value is false. If this value is not set, Flex
does not use the proxy.
Channels
Flex now requires that you specify a channel to define the way data is transported for each
RPC service destination. Service requests and responses are now messages. Messages are sent
and received on a channel, which represents a logical connection to a destination. Channels
define a protocol and a port.
Each channel corresponds to one network transfer protocol that Flash Player supports. For
example, the AMF channel uses the AMF format over HTTP and the HTTP channel uses a
text-based format over HTTP.
- 4Contents 4
- Contents 5 5
- 6Contents 6
- About Flex Documentation 7
- Typographical conventions 8
- Getting Started 9
- Step 1: Find and replace 10
- Application namespace 11
- Color value formats 11
- Alpha and scale properties 12
- Event.currentTarget 12
- Uninitialized values 12
- Replace _root 13
- Step 2: Add access modifiers 14
- Step 3: Add types 15
- Step 4: Update events 16
- Step 7: Update data services 18
- Step 8: Charts 18
- Step 9: Overrides 18
- Step 10: Binding 19
- Step 11: API updates 19
- 20 Getting Started 20
- ActionScript 2.0 to 3.0 21
- Usability improvements 22
- Capitalization of identifiers 23
- Package reorganization 23
- Accessors 23
- Socket.isConnected property 24
- Classes and packages 25
- Using packages 26
- Using classes 27
- Using external files 28
- Initializing variables 29
- Default values 30
- About undefined 31
- Explicit typing 32
- Type detection 33
- Primitive types 33
- Non-assignment expressions 33
- Global functions 34
- Function changes 35
- Deprecated features 35
- Miscellaneous 36
- Metadata 37
- Constants 38
- Method signatures 38
- __proto__ 39
- Working with keys 40
- LocalConnection 40
- Flex Classes 41
- Core classes 42
- Member Change description 43
- The addEventHandler() method 50
- The load and unload events 51
- Validation and layout methods 51
- Drawing methods 51
- 52 Flex Classes 52
- Containers 53
- Controls 61
- dataTipOffset 77
- Flex 1.x: 79
- This class has been removed 87
- Formatters 89
- Managers 91
- Media controls 94
- Printing 94
- Resources 95
- Service tags 95
- Callback URLs 97
- Utilities 99
- 100 Flex Classes 100
- Data Providers 101
- 102 Data Providers 102
- 104 Data Providers 104
- About binding 105
- Binding from a property 106
- Binding from a property 107 107
- 108 Binding 108
- Binding from a property 109 109
- Binding with Arrays 110
- Contents 111
- About events 112
- Component startup life cycle 112
- Migrating the Event object 113
- Using static constants 114
- Using function listeners 115
- 116 Events 116
- Maintaining scope 117
- Using setCapture() 117
- Keyboard events 117
- 118 Events 118
- Styles and Skinning 119
- Using the StyleManager 120
- data-tip-offset 121
- CSS class selectors 122
- Global style sheet 123
- Using type selectors 123
- Using skinning 124
- Skinning assets 125
- Drawing programmatic skins 125
- Using embedded fonts 126
- Themes 127 127
- 128 Styles and Skinning 128
- Behaviors 129
- Overview 130
- New Behaviors syntax 131
- 132 Behaviors 132
- New Behaviors syntax 133 133
- New events for effect classes 134
- Data Services 135
- Proxy use policy 136
- Channels 136
- Unnamed RemoteObject 137
- Flex 1.5 syntax 138
- Flex 2 syntax 138
- Named RemoteObject 139
- Unnamed HTTPService 140
- Named HTTPService 142
- Unnamed WebService 143
- Named WebService 144
- Login commands 150
- RemoteObject 152
- Configuration and Command 153
- Line Tools 153
- Configuration files 154
- Security 155
- Command-line compilers 156
- SWD files 158
- Breakpoints 158
- Commands no longer supported 159
- Customizing Components 161
- Specifying the package 162
- Defining the class 162
- Defining the constructor 162
- Creating bindable properties 162
- Overriding a method 163
- Clip parameters removed 163
- Renamed invalidateStyle() 163
- 164 Customizing Components 164
- Additional Migration Issues 165
- Renderers 166
- Charting 167 167
- Interfaces 168
- Cell renderers 169
- Validators 170
- Deprecated item New item 171
- Embedding resources 172
- Migration Patterns 173
- Instantiating Flex controls 174
- Using mixins 175
- 176 Migration Patterns 176
- 178 Migration Patterns 178
- Other issues 180
- Setting actions 181
- Using Timer 182
- Accessing request data 183
- Using the Preloader 183
- 184 Migration Patterns 184
Produits connexes et manuels pour Manuels des logiciels MACROMEDIA FLEX 2-MIGRATING APPLICATIONS TO FLEX 2
(412 pages)© 2020, manymanuals.fr. Tous droits réservés | 0.035 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Commentaires sur ces manuels