As in my earlier post I mentioned, Fiber is a suite of technologies which helps you do model driven development using Flash Builder 4 (with modeler plugin) and LiveCycle Data Services 3. And the major part of the Fiber is the Adobe Data Model, which lets you build data models, create services and bind services to data controls. Below are the slides attached which I used at the TAC 2009 and also find attached source code which was used for demos at the conference.

In order to work with attached codes, you will first need to setup and get started with Livecycle DS 3, about which you can find it here.

Demo II : Getting started with FB4 & LCDS 3
Demo III : Working with Annotations & Styles
Demo IV a : Working with Filters : Criteria based Filters
Demo IV b : Working with Filters : Pass-through Filters

Model Driven Development using LCDS 3 – Annotations & Styles from Mohammed Khan on Vimeo.

You can download the the source code which was used in the above screen cast here, and the sample MySQL database script here. When importing the project into your Flash Builder 4, you will need to change the LCDS 3 turnkey path in the Flex Compiler settings, also the RDS username and password would change accordingly. If you have any issue in getting started, feel free to share.

Getting started with Model Driven Development using LCDS 3 from Mohammed Khan on Vimeo.

UPDATE: The next part of this screen cast titled “Model Driven Development Using LiveCycle DS 3 Beta – Annotations and Styles” is available here.

1. Execution runtime support for Adobe Data Model

With the introduction of Fiber, a suite of technologies that enables Model-Driven-Devleopmet using Flash Builder 4 and LCDS 3, also comes Adobe Data Model. Adobe Data Model, is an XML-based persistence modeling language, and under the hood it implements the Java Persistence Query Language (JPQL) which is part of the Java Persistence API (JPA). In order to work with Adobe Data Model, you will need Flash Builder 4, Modeler Plugin, and LCDS 3 Beta. Without LCDS 3 Beta, you will not be able to execute or deploy your data model definitions, this also means Adobe Data Model wouldn’t work with BlazeDS.

2. Data throttling

For developers who worked with Flash Media Server, this should not be new. Throttling means the server increases or decreases the amount of data streamed based on how much the Flash Player can consume and process. LCDS 3 beta has various throttling mechanisms, and the one that automatically controls the server’s data outflow rate based on the client consumption rate is known as Adaptive Throttling.

3. Reliable Message Transactions

In LCDS 3, the Quality of Service (QoS), has been largely improved, for instance when working with data transactions applications like a Banking App, its necessary to have an acknowledgement made at all ends of the the data pipeline. This guarantees that whatever is send/receives is reliable.

4. Recover over Network Failures

Another feature that has been added to improvise the quality of service, is the ability for the Flash Player clients to recover data over network failures. A particular business case where this feature can be handy is a Trading application. Data Transmission is crucial in any data driven application, and also it becomes necessary to have high network redundancy. With multi-tier features it makes it possible for the Flash Player client to switch sessions with different LCDS 3 server definitions, if an network failure occurs with a particular destination.

5. Pause/Resume Capabilities

Another interesting feature, which can change the way the Flash Player client handles large chunk of binary data transmission is the Pause/Resume capability. Exchanging documents, large set of data can be controlled in more orderly fashion, the user gets the ability to control the exchange of data.

If you feel the above features excite you and want to test drive the MDD feature of LCDS 3, watch for this space. Till then I hope you have a great time.