
Build a distributed application with the Java adapter 235
View the server-side Data Management Service
destination
The lesson2.mxml file contains a DataService component that takes the name of a server-side
Data Management Service destination named
contact as an argument in its constructor.
This reference to the contact destination is the only thing the client application needs to
communicate with the destination. The
contact destination is defined in the data-
management-config.xml file in the WEB_INF/flex directory of the samples web application.
The following example shows the XML code that defines the destination:
<destination id="contact">
<adapter ref="java-dao" />
<properties>
<source>samples.contact.ContactAssembler
</source>
<scope>application</scope>
<metadata>
<identity property="contactId"/>
</metadata>
<network>
<session-timeout>20</session-timeout>
<paging enabled="false" pageSize="10"/>
<throttle-inbound policy="ERROR" max-frequency="500"/>
<throttle-outbound policy="REPLACE" max-frequency="500"/>
</network>
<server>
<fill-method>
<name>loadContacts</name>
</fill-method>
<fill-method>
<name>loadContacts</name>
<params>java.lang.String</params>
</fill-method>
<sync-method>
<name>syncContacts</name>
</sync-method>
</server>
</properties>
</destination>
Reference to a Data Management
Service adapter configuration; this
destination uses the Java object adapter
Java class that carries out data fill and
synchronization operations between
client and server.
Network -related settings
Mapping to method on
adapter class to get data.
Mapping to method on adapter
class that synchronizes multiple
versions of data.
Comentários a estes Manuais