Watch me speak on BlazeDS, Flex and Java integration. (Original Post on DZone: Meet the Author – Shashank Tiwari on BlazeDS, Flex & Java Integration).
Getting Started with BlazeDS, a DZone RefCard on Adobe BlazeDS that I authored is available online. Go ahead and download it now.
The great thing about the DZone RefCards is that they are terse and useful presentations of technical topics and are available completely free of charge. The RefCard on BlazeDS is a quick 6 page practical introduction to some of the key aspects of using BlazeDS. For more details, consider reading my book on Adobe BlazeDS — Professional BlazeDS (Wiley/Wrox, 2009).
Please let me know if you find the RefCard useful. Also, please point out to me any errors that may have slipped through the cracks.
Igor Costa has invited me as a guest on the next episode of SextaFlex, the Friday talk show on Flex. I speak about combining Flex and Java using BlazeDS. My talk is around my new book Professional BlazeDS (Wiley/Wrox, 2009).
If you wish to understand how best to combine Flex and Java and extend the power of BlazeDS to support production grade scalable applications then join the SextaFlex session this Friday, October 23, 2009. The session will be delivered over Adobe Connect, which you can access online at http://experts.na3.acrobat.com/palestras/.
Creating Rich Internet Applications with Flex and Java
My new book on “BlazeDS” was released earlier this week. I got my first set of author copies last night in the mail. It was a great feeling holding a copy in my hand. This book was written over the last many months as I toiled with a number of other things, including working on client projects, at the same time. Most of the writing was done in the nights and weekends. I must at this point mention that my family (wife and kids) was extremely supportive else this book would have never been possible.
The book covers a lot of ground at the sweet intersection spot where Flex based RIA and Java meet. It covers the fundamentals of the wiring, protocols, formats and the API that relate to the integration of Flex/AIR and Java in the first few chapters and then rapidly graduates to explaining advanced topics. Advanced topics include Spring and Hibernate integration, custom adapters and real-time data push. As the topic clearly suggests all integration discussion is in the context of the open source data services product from Adobe: BlazeDS.
If the subject of integrating Flex/AIR and Java interests you, then go grab a copy of this book from your local technical book retailer or order online at Amazon – http://www.amazon.com/Professional-BlazeDS-Creating-Internet-Applications/dp/0470464895/. As you read the book, please let me know of any errors. If you like the book, please rate it well on Amazon and/or leave a comment behind.
Hope the book helps the folks who are actively combining Flex (or AIR) and Java to create the next set of rich and robust productivity enhancing enterprise grade applications.
If you are someone who is interested in coupling Flex and Spring based messaging (especially JMS) systems, you may want to whet your appetite by reading my article on the subject at DZone. Here is the link: Integrating Flex and Spring based JMS applications. Please let me know if the article was helpful or want to learn more about the subject.
Unfortunately, friendsofed.com is unavailable!
Where you could normally see tons of information on books they had published, code downloads associated with those books and more, stands a page advertising domain renewal services. This is what the page looks like today –
friendsofed.com Hosed!
I was made aware of this rather awkward situation by readers of my book Advanced Flex 3. The site is down means they can’t get hold of the code for the examples in the book anymore. Oops! that no good.
So I am writing to inform all my readers of the following:
That’s all for now. Thanks for your patience.
Thanks to our publishers friends of Ed (APress), we are giving away 4 copies of Advanced Flex 3 at MAX 2008 next week. Stop by at the 360 | MAX booth, where you will surely find Tom and John (and me, many times in the day), and register to enter the daily raffle. You enter the raffle once and remain a hopeful for all three days. We will pick one winner (and two on the last day) randomly from the list of registered folks everyday and announce the winners right then. The winner goes out of the list and the rest are all carried forward to the next day. So the earlier you enter the better chance you have of winning. Good luck!
Advanced Flex 3
Advanced Flex 3
My book — Advanced Flex 3 — is out in the market! It was a good feeling to hold the printed version in my hand, as its first few copies arrived yesterday. We celebrated at home with some delicious brownies that my wife baked right then. Months of work and lot of night-outs have gone into writing it. (Book writing can make you sleepless!).
Its one of the few (or maybe only?) books which addresses the needs of the advanced Flex developer, who is interested in creating enterprise grade robust applications. Hopefully it is as enjoyable reading, as it was writing it!
It was a great experience working with my co-authors (Elad, Jack and Joshua) and having my wife and kids support me through the entire process. Not to forget my parents and in-laws supported me too, ’cause I was busy writing even on vacation in their homes. (Book writing can make you ill mannered 
)
The book is available at Amazon, Barnes and Noble, Borders, bookpool , Springer and SamedayBooks (UK).
As you read it, please let me know what you think of the book. I am eager to hear from you!
This article is published on JavaLobby / Dzone.
Seam is an interesting web framework that integrates the different pieces of the application stack and incorporates ideas from rules engines, BPM engines and SOA into regular application development. In this article, the focus is on Seam’s navigation and flow related features. Let’s see how they could play out in practice.
The article logically divides the topic into two parts, which map to the two navigation models, namely stateless and stateful. In Seam, stateless implementation uses JSF style pageflows while the stateful implementation uses jPDL pageflows.
Navigation from page to page, or view to view, in a web application can either be agnostic to or be governed by the state of the application. In other words, it could be stateless or stateful. In a stateless model a set of rules map action or event outcomes to specific views or pages. On the contrary, in a stateful model the navigation rules define transitions from one state to the other, which in the process causes transition from one view or page to the other. You may ask why navigation models need to be stateful at all and you may also ask how the state information could be tied in with the navigation rules. Both the questions are pertinent and important so I will try and answer them right away.
In a process driven web application the flow from one page to the other is often governed by the application state and the decision tasks which use this state information. As an example, consider a loan processing application manifesting as a web application. In this application a user could be transitioned from the “welcome page” to the “loan information capture page” or “modify and confirm information page”. The choice of the page to transition to will depend on the applicant being an existing approved customer or not. An existing customer would be sent to the “modify and confirm information page” since most information pertinent to the loan processing is already available, while a new customer would be directed to the “loan information capture page” as basic information needs to be available before any further decisions can be made. Assume that such an application also gives the user a choice to upgrade its approval status. As an example the particular user may be approved for loan upto $500,000 but now needs to upgrade the loan approval amount to $1 million. In this example at the “modify and confirm information page” the user will choose to upgrade the loan amount and so would be diverted to “get additional information page”. You see what is happening here, the navigation is essentially mirroring the viable transitions which depend on the current state of the application. It’s a state transition scenario, that’s it! This flow is depicted in Figure titled: “The loan approval application process flow”.
 |  |  |  |  |  |
 |  |  |  |  |  |
 |  |  |  |  |  |
 |  |  |  |  | |
Powered by FireStats
0