MACROMEDIA FLASH 8-FLASH, Руководство пользователя

Страница: 447 / 678

Advanced topics in data integration 447
To add a binding using path expressions:
1.
In either the Add Binding dialog box or the Bound To dialog box, select Use path
expression.
2. Enter a path expression to identify the schema item to which you want to bind. Path
expressions are entered in the following formats:
■
For properties that contain ActionScript data, the path follows this format:
field [.field]...
In this format,
field
is equal to the name of a field (such as
addresslist.street
).
■
For properties that contain XML data, the path follows this format:
XPath
In this format,
XPath
is a standard XPath statement (such as
addressList/street
).
3. Click OK to return to the Bindings tab.
Default data binding events
When you use the Bindings tab to create a binding between two components, the binding is
triggered by the default component event. If you want a binding to execute independently of
the default component event (which is predetermined by Flash), you must manually refresh
the binding with ActionScript code. For more information, see “ComponentMixins class
(Flash Professional only)” in the
Components Language Reference (in particular, see the
ComponentMixins.refreshDestinations()
and
ComponentMixins.refreshFromSources()
methods).
In general, for UI components, the
change
or
click
events are the default events used to
trigger data bindings, such as
TextInput.change
,
Button.click
,
RadioButton.click
. For
connector components, the
result
event triggers the binding, such as
XMLConnector.result
.
Server-side requirements for resolving XML data
This section describes requirements that your server code must fulfill when receiving results
from an XUpdateResolver component. It contains information relevant for the server
administrator who is handling server-side functions for your Flash application.
After the server finishes with the update packet, either successfully or unsuccessfully, it should
send back to your Flash application a results packet containing errors or additional XML
updates resulting from the update operation. If there are no messages, the results packet
should still be sent, but it will have no operation result nodes.