Content Inside :
The Flex Data Management Services automate the process of synchronizing data between the client application and the middle-tier. The changes made to the data at the client-side are automatically sent to a service running in your application server. This service then passes the changes to your business layer or directly to your persistence layer, whatever your persistence solution is: DAOs with straight JDBC calls, Hibernate, EJBs, JPA, iBatis, or any other solution. This tutorial assumes that you meet the following prerequisites: • Knowledge of server-side Java development and the structure of a J2EE web application • Familiarity with SQL and JDBC • Basic experience with Flex development • Basic experience with Eclipse. Create a Java project There are several ways you can set up Eclipse to work on the Java classes of a Web application. You can use a simple Java project, work with the Web Tools Platform (WTP), or other plugins like MyEclipse. In this tutorial, to avoid dependencies on a specific plugin, we use a simple Java project. Create a Flex project 1. In the Eclipse menu, select File > New > Project 2. Select “Flex Project” in the project type tree and click Next 3. Fill in the “Create a Flex Project” page of the wizard as follows and click Next. Creating the Server Side The changes made to the data at the client-side are automatically sent to a data service running in the application server. The data service then passes those changes to an object called the assembler. The role of the assembler is to pass the changes, in the appropriate format, to your existing business objects, or directly to your persistence objects. The assembler class is the only class that you have to write at the server-side (in addition to your existing business and persistence objects), and is typically a very simple class.
If you see unrelated pdf files with the description or copyrighted material published, please report to us, we'll correct/delete it it as soon as possible.NONE OF THOSE MATERIALS ARE HOSTED IN THIS SERVER NOR UPLOADED BY ME IN SOMEONE'S SERVERS.  Read our DISCLAIMER for more detail.
We are neither affiliated with authors and brands nor responsible for its content and change of content.
Information contained herein is provided "as is" without warranty of any kind, either expressed or implied, including any warranty of merchantability or fitness for a particular purpose. In no event shall ANYONE be held liable for any loss of profit, special, incidental, consequential, or other similar claims.