Flex on Java update

18 04 2009

Over the past few months my co-author and I have been working hard at reworking much of what we have already written for our book in order to hopefully result in a much better book for our readers. Earlier today Manning released a letter explaining the delays in any updated chapters to those who have purchased a MEAP subscription to our book. The letter reads as follows:

We would like to take a minute to personally update you on the progress of our book. Although we are running behind the originally estimated release date, the end product will be a much better learning experience. From the beginning we have been continually refining the book and have taken the great feedback we’ve received to align the book more closely to your thoughts and insights. If you are receiving this letter and were part of the reviews, THANK YOU! Much of the feedback received, all helpful, really matched with how we (the authors) were feeling and helped us to really home in on what we felt would be important to include. Here are just some of the things that can be expected out of the new and improved Flex on Java.

Developer accessibility
When we started the Flex on Java journey we wanted to write a book that would assist Java developers in refactoring Java applications with the richness of Flex. Unfortunately, the sample application wasn’t a good fit for everything we wanted to teach and was absorbing too much of our time trying to make it work properly for the readers. The sample application was an open source product that was not easy to download, build and go. This issue caused us to rethink our approach and we turned to Matt Raible’s AppFuse framework that is aimed at helping developers build applications quickly and efficiently. AppFuse makes deployment and creation of the sample application a breeze and also opens the door to developers who are new to Java. It allowed us to focus more on the topic of integrating Flex with Java while broadening its audience to those who are not Java or Flex gurus.

Hit the ground running (faster pace)
The free chapter available will become an introduction to the book and chapter 1 will now get readers rolling with development on the first page. Chapter 1 will begin with developing the server-side application with the AppFuse framework and then quickly begin integrating Flex in chapter 2.

Deepening focus on Flex integration with Java
The faster tempo and more narrow focus on the topic of Flex and Java integration allows us to quickly go deeper in that topic. We will discuss how to use BlazeDS to connect to the Java server-side including POJO services, Spring services and Spring security in more detail. We will also include working with real-time JMS applications utilizing the Flex and Java APIs.

More focus on scalable frameworks
Good developers move from technology to technology and look for frameworks that allow them to avoid the common problems when designing an application. Frameworks for doing both dependency injection for creating loosely coupled applications and Model-View-Controller (MVC) will be explored in more detail. Frameworks such as Spring ActionScript, Cairngorm, and Pure MVC (and possibly others) will be demonstrated.

House cleaning
There are other topics like building the application with Ant and setting up continuous integration that are important but not part of the main gist of the book, so we moved those topics into the Appendices of the book. There are other housecleaning items that are being performed to make this the best book possible on integrating Flex with Java.

We hope that you will be delighted with the upcoming changes to the book. Please feel free to provide us with any feedback you may have for us. Thanks again!

Sincerely,
BJ Allmon and Jeremy Anderson
Authors of Flex on Java





New issue of GroovyMag

3 04 2009

April’s issue of GroovyMag has finally been released, and I must admit that I was pleasantly surprised when I found out that my article “Get Rich Quick with Flex & Grails” was to be the feature article for this issue. Please help support this very awesome magazine and purchase a copy of April’s issue here (http://www.groovymag.com/main.issues.description/id=8/).gm6_400





GroovyMag article finished

13 03 2009

Earlier this year at CodeMash, my co-author BJ had lunch with the editor of GroovyMag, Michael Kimsal, and discussed writing an article for his magazine, unbeknownst to me.  Ironically at the same time I had been scheming and sending emails to Michael as well pitching the idea for an article on integrating Flex with Grails.  Long story short we landed a 2 part article for the upcoming April and May issues of GroovyMag.

If you’ve never heard of GroovyMag, I strongly encourage you to check it out.  It’s a very reasonably priced magazine for Groovy and Grails developers available as a PDF for the low price of $5 per issue.  Considering there are almost no advertisements and each issue is packed with great content from authors such as Chris Judd, and of course now yours truly.





Agile 2009 submission: Functional Testing Flex

27 01 2009

I threw my hat into the ring this morning with this submission to the Agile 2009 conference (http://agile2009.agilealliance.org/node/579).  Please check it out and submit any comments you may have as I refine the proposal.





Flex on Java to now leverage AppFuse

18 01 2009

Well the 2/3 review of the book I’m currently writing, Flex on Java, has just been wrapped up and we’ve gotten some wonderful feedback from our reviewers, both good and not so good.  I’m learning that the not so good reviews are sometimes more useful in helping us to refine and improve the book in the long run.  More than one reviewer had commented, and I had started to believe this myself before the review even began, was that the sample application that we had decided to use was too cumbersome and involved too many workarounds to make it work.  Read the rest of this entry »





Resurrecting XPlanner

7 08 2008

As you may have heard, I am currently writing a book (http://manning.com/allmon) on how to integrate Flex into a Java based web application.  When we started this project, we had many ideas for what we were going to do for a sample application to use throughout the book.  Too many titles out there either use trivial or incomplete examples that work well to showcase as much of the technology as possible but usually fall short in giving the user a clear picture of how to develop an end-to-end solution.  So my co-author and I, through suggestion from a fellow developer, decided to base our sample application on the XPlanner project.
Read the rest of this entry »





New Flex Maven plugin on the block

26 03 2008

I’ve recently discovered a new player in the Flex/Maven plugin game called Flex Mojos.  This one is slightly different than the other ones that I’ve seen in that it’s using the new Java based compiler API just released with Flex 3.  One nice side effect is that it appears to be much faster than the previous plugins.  I’ll be keeping my eye on this one to hopefully implement a decent integration with FlexUnit or even better FUnit.





What did I get myself into now…

12 03 2008

Well, it’s now official, I’m writing a book. I’ve signed my contract, and there’s no turning back now. “You’re going to do what?” you may ask. My friend and cohort here at Pillar, BJ Allmon and I have begun the adventure of writing our first book, our first not only writing together but our first for each of us, tentatively titled “Flex on Java” for Manning Publications. Yes, Manning, you know those guys with all the great “In Action” books with the funny looking people on the covers. I’m really excited about this because I’ve always felt they put out good quality books, let’s hope that we don’t ruin that trend.

Read the rest of this entry »





Refactoring to RIAs – Agile 2008

30 01 2008

BJ and I have decided to throw our hat into the ring and submitted a session proposal to the Agile 2008 conference. You can read about it and comment on it on the Agile 2008 submission site here (http://submissions.agile2008.org/node/1676), or I’ve copied the summary below.

In 2002 Macromedia used the term “Rich Internet Applications” (RIA) to describe the next generation of web applications that have all of the benefits of a traditional desktop application, with the flexibility of being deployed via the Internet.

However, it’s 2008 and RIA has not been able to penetrate the business application sector with any real success. The old days of RIA are history. (Maintenance nightmares, weird or no unit testing, and little friendliness toward other agile developer practices.)

Read the rest of this entry »





Continuous Integration with Flex

16 01 2008

Earlier today I had posed a question to a mailing list in the .NET community asking about Continuous Integration with Flex in the .NET world. After a couple of answers from people who obviously did not understand the question, because they just told me to google CruiseControl.NET, someone with some knowledge of TDD and Agile practices stepped up and pointed out the obvious point I was trying to make. There currently is no real good way to automate your FlexUnit tests in such a way that a CI server like CC.NET or HudsonCI would know whether or not all of the tests for your Actionscript classes passed or failed.

So I’ve decided to start a Google Code project called agile-flex, where a couple of other developers and I will attempt to build some agile tools for the Flex framework, starting with a test runner that will help enable continuous integration for Java, .NET, or even just plain old Actionscript. The runner will likely be based off an article I found from Aaron Spjut here. In a nutshell we will create a test runner in Adobe AIR that will generate XML output similar to JUnit and NUnit for the CI server to be able to interpret. This will also enable the generation of report artifacts using the JUnit Report tasks or even a custom XSLT if desired. I’ll post more details as the project continues.

UPDATE… The Flex-Mojos project now fulfills this need, so I’ve deleted the Google Code Project that we started for this.