Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Expert Spring MVC and Web Flow (Expert's Voice in Java) Paperback – February 23, 2006
ITPro.TV Video Training
Take advantage of IT courses online anywhere, anytime with ITPro.TV. Learn more.
Frequently Bought Together
Customers Who Bought This Item Also Bought
About the Author
Colin was first introduced to the Spring Framework in January 2003 by his mentors, Peter Den Haan and David Hewitt, and he has never looked back. After a couple of years using the Spring and Hibernate technology stack to good effect, in May 2005 he became one of the early adopters of Spring Web Flow, finally finding the missing item in the web development toolbox. A self-confessed addict of the green bar that comes from following test-driven development and XP, Colin regularly frustrates new team members by introducing a continuous build environment.
When not hanging around the Spring support forums (http://forum.springframework.org), Colin can be found out walking with his wife and two dogs, practicing martial arts, attending his local church, or preparing for the arrival of his first child.
Seth Ladd is a software engineer and professional Spring Framework trainer and mentor specializing in object-oriented and testable web applications. He started his own company building websites at age 17, but now enjoys having a real job. Currently working for Camber Corporation, Seth has built and deployed systems for NEC, Rochester Institute of Technology, Brivo Systems, and National Information Consortium. He has architected and developed enterprise applications in Java and C for both the server and remotely connected embedded devices. He enjoys speaking and teaching, and is a frequent presenter at local Java user groups and at corporate developer conferences. Seth is very thankful for living and working in Kailua, Hawaii, with his wife.
Steven Devijver is an experienced Java developer who started developing J2EE applications in 2000. In 2003 he discovered the Spring Framework, and since then he has been one of its most enthusiastic users. Steven is a senior consultant at Interface21, teaching hundreds of students every year about the Spring Framework.
Darren Davison is a principal consultant for UPCO, specializing in J2EE and open source Java technologies. He has been involved with Spring since the summer of 2003, well before its 1.0 release, and he used the framework to underpin a global intranet site for an investment bank. Darren has previously worked for multinational manufacturing and engineering companies on e-business, infrastructure, and many web-based projects. Away from work, Darren enjoys the never-ending journey of discovery that is GNU/Linux. When not in front of a computer screen, he likes reading and any form of live entertainment.
Top Customer Reviews
The other thing that I really didn't like was the disorganized fashion with which the examples were presented. The authors seemed to jump around describing one small section of the problem in great detail, then 3-4 pages later would give you the critical piece of information you needed to understand their example 3 pages before. I am a fan of examples that are logically presented:
First you do x,
Then you do y,
you configure x to point to y
now deploy it, type this in the url field, and there you go, it works.
I found these examples to be more like:
First you do x,
then let me tell you everything there is to know about x.
y is very important as well.
if you wanted to set up y you could do it like this.
of another popular way of configuring y is like this.
and then there's this thing called z.
z is also very important, and here's some more information about z.
But of course, before we can set up z, we need to configure x to point to y.
I'm sure you can figure out how to configure x and y.
that's it, we're done.
So when you're done reading you feel like you have increased your general knowledge of the subject, but you really don't know exactly what you're supposed to do to actually make something that works.
I also would have liked more information about using commons-validator with Spring MVC instead of so much detail on VaLang. This would have been especially helpful for people moving from Struts to Spring MVC.
Those are the negative aspects of the book. On a positive note, it is fairly well written.Read more ›
Today, an abundance of MVC frameworks - each with its own pros and cons - plague a web-developers decision to choose one. Out of them, frameworks like Struts, Webwork and Maverick are deemed as request-driven frameworks, where as JSF and Tapestry are deemed as component-driven frameworks. Request-Driven broadly means, that the framework does not hide the HTTP-ness of the web world, but provides absractions that can simplify your job to handle them. Component-Driven means, that the web-framework seeks to hide the HTTP-ness, and provides the developer with an abstraction equivalent to Swing programming. Both types of frameworks have their own advantages and disadvantages. Spring MVC falls into the request-driven web frameworks category.
In my career, i have worked with many web frameworks. Out of all of them, i prefer Spring MVC for the following reasons
1. It has access to the full power of the Spring IoC and AOP container.
2. It is very well architected and brings true seperation of model, view and controller better than any other framework out there.
3. It is highly customizable.
4. It is interface driven, and doesnt force you to extend any framework classes.
5. It is easily testable - both unit and integration tests.
6. It helps apply good OO principles to the web-tier.
7. It provides easy-to-use template implementations of basic workflows.
8. It provides support for various view types(JSP, Velocity, Freemarker, etc) and completely decouples this support from other parts of the MVC.
9. It provides an exhaustive set of interface based hooks that one can customize or freshly implement for their own purposes.
10.And many more...Read more ›
The only part of this book that is very well written is the chapters on Spring Web Flow. Indeed, it appears that the chapters were written by someone other than the authors of the rest of the book. Someone who understood and appreciated the importance of a very thoughtfully organized FLOW of any sequence of logical steps, be it a software application, or a flow of information such as an instructions manual, or a tutorial. That's why Colin Yates, the apparent main contributor to Chapters 11 and 12 (on Spring Web Flow), does a much better job than the rest of the authors. Unfortunately, those Web Flow chapters are largely obsolete today. Some code in the book won't work. You'll immediately see that the classes in the org.springframework.webflow.Read more ›
Most Recent Customer Reviews
Besides being out-of-date in a rapidly changing field, and having organization flaws mentioned by others, what I found most frustrating was that if you take the time to enter the... Read morePublished on January 29, 2014 by Rick Grover
Simple language, explains the reasons why the framework is build so. Plenty of examples.
Love the book. It is a must have.
First, to much usual "architectural" blah-blah and marketing, copy-pasted from other books like this. Read morePublished on April 18, 2013 by Dimitri K
I had trouble getting what I needed out of this book. It was a little unorganized and fragmented.
I suggest Spring Recipes.
Learning Spring is a valuable undertaking, and this book was one of the better books I have read. I would suggest another book to cover the Spring fundamentals, as this book is... Read morePublished on July 7, 2010 by Colin Sulin
I think the author is technically good but very shabby & lazy! .. as usual with developers (including me). Thats why developers dont make good authors. Read morePublished on April 2, 2010 by Ronn Macc
I bought this book with the hope of getting a better idea of how I should build the Web Flow flows in my Grails ( [...]) application. Read morePublished on August 4, 2008 by Keith