Enterprise Development with Flex

It’s been almost four months since our book “Enterprise Development with Flex”  been released in print by O’Reilly.  Since day one, it remains in Amazon’s bestseller’s list in several IT categories. This gives me a great feeling given the fact that Amazon re-calculates their stats hourly.
I’d like to share with you some interesting facts that from the times when this book was in its proposal stage. If you carefully look at the book cover, you’ll notice a little logo and the text Adobe Developer Library.  To earn the right to be included in this library our book proposal had to be approved by Adobe engineers. We made it, and are grateful to excellent software engineers from Adobe Flex team, who put their trust in our ability to write such a complex and advanced book.

After the approval process was done, O’Reilly sent us the Flex team members feedback without revealing the names of engineers who wrote them. Most of them were 100% positive. But our special thanks go to one unknown member of Flex team who wrote something like, “I don’t agree with many of the things that these authors write about Flex in their blogs and articles, and I’d rather not approve them, but I will because there are not many people in the industry who are capable of writing such a book.” We don’t know your name, but we consider this assessment to be the best compliment we’ve received so far.

Looking forward to meeting with the members of Adobe Flex team in October at MAX conference.  The authors of this book are going to attend this event in LA in October.

Our praise goes to the O’Reilly cover designers who correctly visualized three authors of this book without ever meeting them in person.

If you bought this book, Farata’s team would really appreciate if you’d spend 10 minutes and publish your review of this book on Amazon. It doesn’t have to be long, but we are looking for getting your honest opinion about our work.

Your truly,
Yakov Fain

Our new Flex book is a Java bestseller

Our new book “Enterprise Development with Flex ” made the Amazon bestseller’s list of … Java books:


This list is refreshed every hour so I’m not sure what place you are going to find it at, but at the time of this writing it’s #20.

Help us to move up the list by doing you know what :)

Podcast: an interview to the RIARevolution

The online publication RIARevolution.com covers everything related to development of rich Internet applications has published an interview with me as a part of the audio podcast Speak Rich. You can download it as an mp3 file or just listen to it at the following Web page: http://bit.ly/2kwOzT

In this interview we are talking about recent Adobe MAX 2009, using Flash for developing application for iPhone, upcoming Flex 4 framework, open source Clear Toolkit framework, the new book on Enterprise development with Flex  and more.

The other episodes of Speak Rich podcast are featuring the following well known software engineers:

Chet Haase, a member of the Adobe Flex SDK team
Stuart Stern, creator of a testing framework Flex Monkey
John Resig, creator of the famous JavaScript library and toolkit — jQuery

You can subscribe to this podcast at http://riarevolution.com/category/speak-rich/

Yakov Fain

One more free chapter from our new book on Flex

A couple of months ago O’Reilly has published this sample chapter of our new book Enterprise Development with Flex. For some reason, they published is as a series of my blogs, but I’m one of three co-authors of this book:

1. http://www.insideria.com/2009/05/chapter-preview-building-an-en.html
2. http://www.insideria.com/2009/05/building-an-enterprise-framewo.html
3. http://www.insideria.com/2009/05/building-an-enterprise-framewo-1.html

Yesterday, one more chapter became available – this time Adobe has published it on devnet: http://www.adobe.com/devnet/flex/articles/flex_performance.html

This book will be printed as a part of the Adobe Developer’s Library. Even though printing of the book is delayed for marketing reasons, you can order an online version of the book over here.

We are using materials from his book during our advanced Flex training. The closest ones are in London in September and in Atlanta.

Yakov Fain

Enterprise Flex: Debunking Urban Myths

I got an email from an enterprise architect considering Adobe Flex as a platform for Web application development in their organization. This email contained a well prepared  list of questions/remarks/concerns that many of enterprise Web architects may face.  That’s why I decided to publish my short answers to these questions. I didn’t change the wording of the questions/ statements.


ActionScript3 is a weakly typed language

This is true, and when I started using it I was also getting angry with Flex compiler that wouldn’t catch my obvious mistake. But as you get more comfy in this environment, you’ll appreciate more and more the flexibility of this language. Most of the developers understand something like

var myCustomer: Customer=new Customer();

But look at the following notation:


The latter instruct the AS3 compiler, “Don’t bother checking if the Customer class even has a property lastName. I know for sure that it’ll be there during the runtime”. Does it look scary? Don’t use it!

Adding a keyword dynamic in the class definition allows you adding properties on the fly. Looks scary? Don’t use it.

To get a better feeling of pros and cons of using dynamic features of the language, read this blog on different styles of programming.

But applications written in dynamically typed languages do require more testing than those written in strongly-typed ones.

AS3 has no support for generics, method overloading, threading, enums, synchronization (handling of a resource e.g. file), annotations.

You need to use a different approach while evaluating domain specific languages vs. the common-purpose ones. Flex is a domain specific language that is not used for developing powerful scalable multi-threaded solutions on the server side. With Flex you are developing just the front end for the applications that are being used by a single user working on his/her computer.
The lack of generics is not a serious drawback (I can live without them in Java too).
Method overloading is not the feature of AS3, but it can be emulated using so called …rest parameter. This is not a showstopper.
From the developer’s perspective, Flex is single-threaded which minimizes the number of mistakes of unskilled (say Java Swing) developers who didn’t put code to refresh the screen into a proper thread, which causes unpredictable results.
Flex has so called metadata markup, which can play the role of annotations. Kinda.
Flex doesn’t support enums, but if this is important for you, consider using a solution offered by Farata Systems in this blog.

For security reasons, the reading/writing in files from Flex application is restricted. In some SharedObject’s may help, but if you need to have full file I/O support consider Adobe AIR.

Difficult to program to enterprise patterns: dominated by event model

While implementing design patterns you should account for specifics of the particular language/environment. Creators of one of the MVC frameworks shoot themselves in the foot by trying to avoid Flex specific event model by introducing more generic Notification class and by implementing Observer design pattern instead of using Flex-specific binding syntax. This approach resulted in creation of overly-engineered and convoluted framework that can be used in several languages, but doesn’t take advantage of goodies available in Flex. You can find some good examples of design patterns implementations in Chapter 2 of the book Enterprise Development with Flex currently available online.

Idiosynchratic binding restrictions and difficult two-way binding; may have been addressed with Flex v4?

The two-way binding is introduced in Flex 4. While being an excellent mean for increasing the productivity of Flex developers, don’t abuse binding. Nothing comes for free and just placing these elegant curly braces actually translates to a bunch of generated AS3 code and may lead to some performance issues in UI-intensive applications.

Poor Collection framework

Yes, AS3 collections are not as advanced as in Java, but they do a decent job if you take into consideration the small size Flash Player where they have to operate.

Generally immature API with numerous traps / pitfalls

ActionScript3 is more than a ten year old language and its current version is stable and doesn’t seem to have more bugs than other languages.

No support for XML schema validation

True. On the bright sight, Flex offers very easy syntax (E4X) for XML handling. But in general, I prefer minimizing using XML, if possible. Sending strongly-typed DTO’s from the server is a lot better way to architect applications.


Validation implementation too simple and not extensible

Consider using validation solutions from Clear Toolkit described over here. Validation solutions are extensible in Flex.

Poor error handling due to asynchronous event firing and separation of MXML and ActionScript in components

I wouldn’t use the word poor here.  When you work in asynchronous mode in any language, techniques for error handling are different. When an asynchronous callback is invoked in Flex as a result of the server side call it comes with an argument containing the error information similar to FaultEvent.

Limited printing support

True.  Consider using extended Flex components from Clear Toolkit that offer PDF generation on the client. Read more in Chapter 11 of the book Enterprise Development with Flex.

FlashPlayer 10 does not run on Windows 98 or Windows ME

So? Would you stick to Java 1.1 just because Internet Explorer doesn’t support any further versions of Java?  Stick to Flex 9 if supporting of older versions of Windows is a must.

Flash Player upgrade/compliance to potentially address bugs etc … is an overhead and will depend on customer willingness to upgrade with any frequency. If a customer refuses to upgrade then what?

As of today, there is no other software in the world that can compare with Flash Player in terms of the speed of penetration. The upgrade is extremely easy.  The customer doesn’t want it…This is a problem in a democratic society. If this would happen in Soviet Union, KGB would simply send him/her to a labor camp in Siberia. This technique won’t work in the current enterprise environment though. Just ignore such customers. I know that some people turn off JavaScript support in their Web browsers, but this is not a good reason for not using JavaScript for Web development.


Poor / complex unit testing of component behaviour

FlexUnit 4 adds a lot more flexibility for those who want it.

Absent integration testing between Flex client and middle tier

This is not true. The proper use of build scripts (Ant or Maven) in conjunction with such continuous integration tools as CruiseControl allows you to set up an environment that fits your needs.

Absent test automation

This is not true. Look at the open source FlexMonkey or commercial tools like QTP or Neoload

Lack of available testing tools
See above


Unimplemented build process automation

You might be tired by now by my suggestions to look at the Clear Toolkit, but it includes Fx2Ant tool that automatically generates Ant scripts for your Flash Builder projects.


Asynchronous platform difficult to code safely to resulting in unpredictable/inconsistent behavior

I see no grounds for such accusations. Asynchronous way of communication with the server side components is implemented in an easy to understand and consistent manner.

Complex event driven MVC model overlayed upon Flash’s own event model
Internal Flex MVC model implemented in some components is typically built using binding and is not complex.

Mixing ActionScript and MXML -> complex, unstructured code (flabby code) – not dissimilar to coding JSPs with moderate to large amounts of JavaScript per file

MXML and AS3 code can be completely separated using various techniques. If you are into design patterns, read about the Code Behind over here.

No automated XML serialization support -> complex error prone data mapping and in some cases tests are the only mechanism to capture errors

I recommend minimizing use of XML in favor of strongly-typed data transferred using AMF or RTMP protocols.

No coding standards/guidelines developed to instruct developer’s on how best to develop, what best practice is etc …

Read about coding conventions here. A number of articles/books on best practices in Flex is already available in this number is growing

Follows same paradigm as HMTL/Javascript

I don’t agree. The main difference is that MXML gets automatically converted into AS3, which in turns gets compiled into bytecode. The byte code runs in the browser-independent VM. This is a huge advantage over developing in unpredictable HTML/JavaScript environments.

Code duplication:

Duplication of model across tiers

I wouldn’t call DTO’s that are traveling between the client and the server code duplication.

Duplication of validation rules across tiers

You shouldn’t program duplicate validation rules on the client and the server. Ideally, your Flex RIA should be developed as a stateful client, and you should apply validation logic accordingly without any duplication.

Technology boundary -> business logic tends to bleed into UI

I wouldn’t use the word bleed in this context. RIA with Flex is like a different incarnation of Client/Server technology. In the desktop world, Visual Basic or PowerBuilder also included a portion of business logic. Popularity of thin Web clients was rather a result of the stateless nature of HTTP protocols then business-driven solutions.

Third party support and documentation:

Incomplete IDE support: no refactoring, poor search functionality, missing many productivity features

Agree.  Flash Builder has room for improvements. IntelliJ IDEA may be considered an alternative IDE for some hard-core developers.

Few / immature third party library support

I know more than a dozen of third-party frameworks used by Flex developers.

Few written examples / templates – or too simple – of Flex in the enterprise
Agree, developers need more enterprise-level books and articles. Flex became a serious player on the enterprise market about three years ago and this explains relatively small number of non-trivial coding examples and case studies.  Flex is very easy to get started with, but unless you have an experienced technical leader on your project the chances are that you may create a poorly designed and slow performing application.

BlazeDS has some problems in relation to session management. We would need to rework the code or wait for a release to fix these problems

Consider re-thinking what data should be stored in a session. Ideally 90% of your session data should be stored on the client.

Client / user experience:

Slower startups due to fat client

You need to learn modularization techniques of Flex applications. Unless you are developing a Hello World type application, it has to have more than one SWF.

Requires Flash runtime @ set version with OS support

The ease of Flash Player upgrade makes this a non-issue


Much lower productivity compared to other frameworks; especially around XML transformation

I’d say that Flex is more productive environment than most others that I know about. I’d highly recommend avoiding using XML as a data format for client/server communications.

Much greater testing required due to asynchronous application behavior; testing is tricky as timing affects the results

True. Plan more time for testing of your enterprise Flex applications. On the other hand, you can extend and customize AMF and RTMP protocols (channels, endpoints, and adapters) and wrap them up into a separate layer to add more security, reliability or some business-specific functionality to create Web applications that are a lot more robust than HTML/JS ones.

Steep learning curve: significantly different programming paradigm to Java web development

I wouldn’t call it a steep, but it’s not as easy as Adobe is trying to present. Get the right instructor or mentor.

Code scatter and poor organization leading to poor maintainability
Any event-driven programming environment may have code scattered in several entities but this doesn’t equate to poor maintainability. Based on my real-world experience in such environments (five years in PowerBuilder, two years in Visual Basic and three years in Flex) I can say that they do not require higher maintenance than Java enterprise projects, which I’ve been developing for 10+ years.

Poorer coding experience

The syntax of ActionScript looks very similar to Java and having declarative language for the UI part (MXML) is a trend in all modern RIA tools like Silverlight or JavaFX.

Proprietary technology

I used to hear this argument a lot back in 2006 when I had to convince AJAX proponents that it’s not the best choice for enterprise application. They used to say that AJAX has lots of open source frameworks and they didn’t want to lock themselves in with a proprietary technology from one vendor (Adobe). It didn’t occur to them that with Ajax, they’d definitely lock themselves in with one of the small vendors of the selected AJAX framework.
Flex SDK, BlazeDS and AMF protocol is an open source software  backed by a large vendor. If you don’t like something – get the code and modify it to as you see fit.

BlazeDS 4 has beta release; should we be investigating this version?

Abode has a history of drastically changing the API of the beta software. I wouldn’t advise to start any serious development with beta projects (the same applies to beta versions of Flash Builder 4 and LCDS 3.0). Keep an eye on the beta software but do not invest too much time in it unless you need some feature badly and are willing to keep modifying your application code with every new maintenance release.

Should we be using RemoteObject rather than XML and finding a workaround for the problem of passing nulls between Flex and Java?

Yes, you should be using RemoteObject not just to find a workaround for some problems, but to lower the network traffic, increase communication speed and work in a strongly typed environment.

Flex 4 has beta release; will this release address any of the issues raised above?

I hope that after reading my answers above you’d agree that the word issue is too strong here. Flex 4 will introduces a new set of components, Flash Builder will get new wizards (code generators) and Flash Catalyst that may improve the designer-developer workflow. But this version doesn’t introduce and revolutionary changes that would affect your decisions to use or not to use Flex platform for RIA. I personally try not to fall in love with any technology, and if I see a better RIA tool that can be used with enterprise applications, I’ll definitely consider it. As of today, I don’t see any serious competition to Flex in this space.

Those who are interested in learning/discussing Advanced features of Flex are invited to attend one of the technical seminars ran by Farata Systems. The closest ones are in London and Atlanta.

Disclaimer. I don’t work for Adobe and won’t be rewarded by them in any shape or form for promoting Flex.  I was never shy before and will not think twice discussing real issues in the design/implementation of Flex framework, but since this tool is better than others in the RIA  domain, it deserves appropriate credits.

Yakov Fain

One approach to Enterprise Flex development

During the last several years our company, Farata Systems have architected and developed a number of Flex projects ranging from creating widgets for startups to large applications having two hundred views. Some projects were created from scratch, and we had a luxury to do it our way. In some cases we had to pick up the code left by other developers.

Three years ago Adobe Flex has been completely revamped (I’m referring to Flex 2) and nobody knew about it. But today, the word Flex doesn’t make Java developers angry any longer. Java/Flex projects are considered business as usual. Many enterprise Java developers went through Flex training and are ready to roll up their sleeves…

After spending 10+ years with Java I can easily put myself in the state of mind of Java developers – they often start with selecting the right framework. As a matter of fact, our perspective customers often request to include an item “Flex framework analysis and recommendations” in the agenda of our very first joint meeting. Here’s a typical conversation that takes place during such meetings:

“Yakov, we have a team of experienced Java developers and some of them have exposure to Flex. Which Flex MVC framework do you recommend? By the way, does the ABC framework support XYZ functionality?”
“No, MVC-based frameworks don’t support any additional functionality that doesn’t exist in Flex. Their goal is to rearrange your code and change the way components of your RIA communicate with each other. But why do you need an MVC framework for your project?”
“Well, everyone’s using them. Having a framework makes the project development more structured and organized.”

Is it so?

Most of the Flex MVC frameworks are intrusive and require developers to write more code just to support the life cycle of the framework itself. Usually, they are built on singletons, and this complicates modularization of the RIA. I’ve been writing and speaking against Flex MVC frameworks for years, and if you’d like to read a detailed analysis and comparison of some of them, read the first chapter of the book “Enterprise Development with Flex”.
Last year at MAX ’08 conference, I participated in the panel “The Flex architecture faceoff”. Two out of four panelists (Chafic Kazoun and yours truly) were advocating component-based approach without squeezing a RIA inside any MVC framework. It was a lively discussion, and you can listen to its recording at http://tv.adobe.com/#vi+f15384v1055
At this point you may say, “OK, it’s easy to critique frameworks, but how do you approach development of a new project especially while having a distributed team of developers with minimal exposure to Flex?”
And I’m glad you’ve asked this question.
In this article I’ll try to identify common artifacts that exist in literally every Flex enterprise project. I’ll also highlight major principles and introduce you to a component-based approach that our developers use in almost every project.

Flex to Java Communication Protocols

The role of Java side of RIA is to deal with data: get the data from a DBMS, a Web Service or any other data source and deliver it to the Flex client as quickly as possible. The fastest way of arranging Java-Flex data exchange is AMF or RTMP protocols. The open source AMF protocol is built on top of HTTP and it offers efficient data serialization between Flex and Java. RTMP offers faster socket-based full duplex communication.

If you install an open source server-side component BlazeDS under a servlet container of your choice, or will use Granite Data Services – AMF will be your only option for data transfer. Commercial LiveCycle Data Services ES (LCDS) will give you both RTMP and AMF implementations. LCDS will also offer you an automated way of data synchronization between Flex and Java.
There is a small number of high performing enterprise applications that would really benefit from using RTMP protocol, and beside using LCDS, an open source server Red5 may become the only alternative.

Note. RTMP protocol is also widely used for streaming video, but these applications are out of the scope of this article.

Challenges of Flex/Java enterprise projects

Let’s dissect a typical enterprise application that’s built with Flex on the client and Java on the server. If you are leading such a project, it’ll present the following tasks, needs, haves, and nice to haves:

1. Keep track of changes that the user makes via UI controls and send modified data to the server
2. It’ll have a number of views that will display the data in the form of grids
3. It’ll have a number of views that will contain forms
4. Some views will represent master-detail relations, i.e. selection of a row in a grid has to display the detail information in a form container.
5. The data grid columns will need custom item renderers ranging from centered checkboxes to dropdowns populated with some reference data by making a separate remote call to the server.
6. It would be nice if a form component could have its own data provider similar to the one that List-based controls use.
7. Data forms must be validated and it would be nice to have
a) reusable validators (i.e. two date fields should be able to reuse the same instance or the Validator object)
b) embedded validators, encapsulated in component such as DataGrid.
8. The main view of your application must appear on the user’s screen ASAP even if they have slow Internet connections.
9. The data changes made by one user may need to be automatically synchronized with the server and notification of the changes should be sent to other users potentially looking working with the same data set at the moment. This functionality is supported by Data Management Services in LCDS, but you may want to have the same functionality in open source BlazeDS.
10. If you are building an AIR/BlazeDS application, you need to come up with a custom solution for automatic data synchronization for occasionally connected applications.
11. Printing is an Achilles heel of Flex. You’d like to be able to generate PDF on the client for your Flex/BlazeDS or disconnected AIR applications.
12. Since your modularized application may consist of five-ten-fifteen Flash Builder projects, writing build scripts becomes a project in its own. Can writing script be automated?
13. Your Flex project may need to consume a dozen or more of Java data transfer objects hence you need to develop the same number of ActionScript classes for efficient data serialization. During the project development cycle the structure of these DTOs may change if not daily, then weekly. An automation tool for generation of DTOs can save you some project development time.
14. Some of the views in your application represent CRUD functionality and using code generators or wizards that lower the amount of manual coding is highly desirable.
15. How do I link all these libraries – RSL/Merge-in/External? Should I use Flex SDK as RSL?

Over the years, we at Farata Systems came up with our solutions to all of the items from the above laundry list. At this point every other reader would exclaim, “Finally, here comes the selling part. I knew it!”
Wrong! All of the components implementing the above functionality not only are available for free, but we also open sourced them as Clear Toolkit framework and (see SourceForge at https://sourceforge.net/projects/cleartoolkit/ ).
Now I will write yet another list of solutions that you might want to research further. By the way, even though we call our components a framework, you can use most of them ala cart.

How we deal with challenges of Flex/Java enterprise projects

We’ve created and are happy to share with the community a number of handy classes, tools, and techniques. You can get the code, which has been open sourced, and you can read our books and articles describing how to use them.

I’ll give you quick references that help in finding solutions to the above challenges (I’ll keep the same order and numbering).

1. Clear Toolkit has a library clear.swc, which has a component DataCollection that supports automatic tracking of the user changes. Look at the ChangeObject class – we’ve implemented it similarly to the one in LCDS, but ours can be used with BlazeDS too. If you need to make your updates transactional, use the BatchService class.
2. We use DataCollection (a subclass of ArrayCollection) as a data provider for data grids. Besides keeping tracks of changes, it encapsulates Flex remoting and reduces the amount of manual coding.
3. Research the DataForm component. Read about it in the sample chapter mentioned at the end of this article.
4. DataCollection supports proper updates in Master-Detail scenarios (see http://flexblog.faratasystems.com/?p=407).
5. Read about resources in the sample chapter mentioned at the end of this article.
6. Read about DataForm component in the sample chapter mentioned at the end of this article.
7. Read about Validator component in the sample chapter mentioned at the end of this article.
8. Read about custom preloaders and how to build every application as a mini-portal with a light-weight starting application in Chapter 8 of the upcoming O’Reilly book.
9. Read about DataCollection in general and hierarchical data collections with deep data synchronization in particular (http://flexblog.faratasystems.com/?p=407)
10. Read about the OfflineDataCollection (Chapter 9 of the upcoming book) and see a pre-recorded demo of a sample application that’s using it (http://flexblog.faratasystems.com/?p=394 ).
11. Explore the Clear Toolkit’s package com.farata.printing – it includes extended Flex components that can expose themselves in a format suitable for PDF generation. Read chapter 11 of the upcoming book for more details and samples.
12. An approach and techniques of minimizing the download time is described in Chapter 8 of the upcoming book.
13. Explore our DTO2Fx code generator that comes with Clear Toolikt: https://sourceforge.net/projects/cleartoolkit/files/
14. Read about Clear Data Builder 3.1 that can generate the entire CRUD application based on either SQL or arbitrary Java DTO’s at https://sourceforge.net/projects/cleartoolkit/files/
15. Read chapters 7 and 8 about linking libraries and loading modules in Flex RIA.

Where can I learn more about these solutions?

First, you can read the book Rich Internet Applications (http://riabook.com/) with Adobe Flex and Java that I co-authored with Anatole and Victor, my colleagues at Farata.
Second, you should read an upcoming O’Reilly book Enterprise development with Flex, written by the same authors.
Third, you may explore the source code of Clear Toolkit components and use the tools published at SourceForge.
Fourth, we invite you to enroll in Advanced Flex trainings, seminars and symposiums that we run on a regular basis. During these events we demonstrate most of the techniques mentioned above as well as our latest findings. Find the up-to-date information about such events under the Training section at http://faratasystems.com/
Fifth, read our blog at http://flexblog.faratasystems.com
To get a better feeling about the functionality of some of the extended Flex components, please read the sample chapter of the upcoming book Enterprise development with Flex. O’Reilly decided to publish this chapter as a three-part blog under my name, but I was only one of three co-authors, and all of us are accountable for these texts. Read the sample chapter here:
Part 1. http://www.insideria.com/2009/05/chapter-preview-building-an-en.html
Part 2. http://www.insideria.com/2009/05/building-an-enterprise-framewo.html
Part 3. http://www.insideria.com/2009/05/building-an-enterprise-framewo-1.html


I just want to give a full credit to my colleagues, excellent software engineers at Farata that work day in and day out on enhancing the functionality of Flex components and decreasing the amount of manual coding required by application programmers. Open sourcing our component have allowed us to bring more people to testing (our big thanks to people who use Clear Toolkit and report issues and make suggestions at Source Forge forums).

We invite Fle and Java developers to become active contributors and submit their version of enhanced components to make Clear Toolkit, a real platform for all who value open source solutions. There are no geniuses that can beat the collective intelligence!

Yakov Fain

Free tickets to AjaxWork in New York City and More


1. As a speaker of AJAXWorld conference (NYC June 22-23), I can invite
anyone as a guest for free (the guest won’t get free lunch or access
to iPhone conf though).

Enter discount code ajaxspeakerexpo at http://tinyurl.com/qtu4b8

My presentation is about occasionally connected applications with Adobe
AIR, Java and BlazeDS: http://ajaxworld.com/event/session/469

2. Preliminary topics for our Second Annual Enterprise Flex Symposium are published at http://www.eventbrite.com/event/355645746.


The Flex seminar in Boston starts next week

Next week, we are running a two-day Flex seminar in Boston. This is one of a kind public event that’s not offered by anyone else. Here’s what makes this event special:

1.    It covers a carefully selected set of topics that are a must to know for anyone responsible of the success of an enterprise Flex project.

2.    The curriculum has been created by practitioners working on real-world Flex/Java enterprise project during the last 3.5 years.

3.    This seminar is delivered by top-notch Flex professionals, certified Adobe Flex instructors and book authors Yakov Fain and Dr. Victor Rasputnis.

4.    This is a small-size event and each of you will have a chance to discuss things that bother you in your current Flex project. We don’t promise and immediate solution, but you can count on getting an honest opinion of an expert in this field.

5.    If you already completed any other training or played with Flex on your own, this seminar is a good next step in your education.

6.    We usually teach this seminar for our private enterprise customers, and we are planning to teach it publicly only one more time this year.

7.    The format of the seminar is a mix of lectures, code reviews and demos. Each participant will receive all the presentation materials used during the seminar.

8.    Last time, Torbjörn Nodin flew to the US all the way from Sweden just to attend this event. This is what he wrote afterward:

If you are considering RIA – be there! If you are considering Silverlight – be there! If you are considering Flex – be there! Even if you have to fly 10h over sea – be there! I did, and it was worth it all.

This time we’ll have one attendee coming from Great Britain.

And all this for less than $600 – readers of this blog get $100 off the price by entering discount code crisisdiscount (for new registrations only).

You still have a couple of more days to decide and book your flight to Boston. For more details and registration visit this Web page: http://www.eventbrite.com/event/295389518 .

An excerpt from our upcoming book “Enterprise Development with Flex”

Here’s an excerpt from chapter 3 of our upcoming O’Reilly book “Enterprise Development with Flex”: http://tinyurl.com/qu5dac

The chapter uses components from the open source component library clear.swc, which is available at http://sourceforge.net/projects/cleartoolkit/ . Although this library is included in the Clear Toolkit, you can download just the clear.swc alone.