Customer Reviews

Pro Java EE Spring Patterns: Best Practices and Design Strategies Implementing Java EE Patterns with the Spring Framework (Expert's Voice in Open Source)

5 star:		(0)
4 star:		(0)
3 star:		(0)
2 star:		(1)
1 star:		(2)

 

 

My impression is that the author had worked on a day job where he participated in converting an old fashioned, outmoded JSP Web App into a JSP Web App that uses Spring to implement EE patterns in vogue back in about the year 2003.
The problem is that EE patterns are a poor fit for Spring. Spring was designed as an alternative to EE that replaces clunky EE solutions with simple, lightweight solutions implemented in a simple J2EE container like Tomcat.
Spring was initially developed as a reaction against the clunkiness and heavy handedness of EE. In this book however, the author demonstrates how to use Spring to implement those features of EE that Spring was designed to replace, not enable.
I did not see any examples in the book of using Spring annotations. Nor did I see any mention of the new Spring taglibs used in Spring 2.x and higher to simplify configuration of transactions, etc.
This book did not add to my knowledge so much as it copy/pasted code examples from the web application he was assigned to on his day job. It was not a fun book to read. It felt at times like reading a very dull, old phone book.
By comparison the book about Groovy by Venkat Subramanium is a real page turner. Groovy, Grails, and Griffon are where the future of web development is going. (The company that develops Spring, SpringSource, has purchased G2One, the company that makes Groovy/Grails, and is folding Groovy, Grails, etc., into Spring).

This book is basically full of the old J2EE patterns, which there is already a classical book that talks about - Core J2EE Patterns. As soon as I saw "Service Locator" in the content table, I can't help laughing (sorry...). The author may be knowledgeable in J2EE, but definitely not in Spring, because in Spring, you don't look up services through a service locator, instead all your dependencies are injected through IoC.

Spring annotations , Spring taglibs all missing !!
The book was published on 2008 Aug , not sure why we are missing the latest topics :-(
Not the best book for architects ... I can not agree.
Overall very dull and poorly written.