- Amazon Student members save an additional 10% on Textbooks with promo code TEXTBOOK10. Enter code TEXTBOOK10 at checkout. Here's how (restrictions apply)
Pro Spring 3 Paperback – Apr 18 2012
Special Offers and Product Promotions
Customers Who Bought This Item Also Bought
No Kindle device required. Download one of the Free Kindle apps to start reading Kindle books on your smartphone, tablet, and computer.
To get the free app, enter your e-mail address or mobile phone number.
About the Author
Rob Harrop is a software consultant specializing in delivering high-performance, highly-scalable enterprise applications. He is an experienced architect with a particular flair for understanding and solving complex design issues. With a thorough knowledge of both Java and .NET, Harrop has successfully deployed projects across both platforms. He also has extensive experience across a variety of sectors, retail and government in particular. Harrop is the author of five books, including Pro Spring, a widely-acclaimed, comprehensive resource on the Spring Framework. Harrop has been a core developer of the Spring Framework since June 2004 and leads the JMX and AOP efforts. He co-founded U.K.-based software company, Cake Solutions, in May 2001, having spent the previous two years working as lead developer for a successful dotcom start-up. Rob is a member of the JCP and is involved in the JSR-255 Expert Group for JMX 2.0.
Inside This Book(Learn More)
Top Customer Reviews
The book is a total waste of money and time.
Most Helpful Customer Reviews on Amazon.com (beta)
(My shortcomings )
a) My background is a developer (then manager), who pretty much lost track of Enterprise Editions of Java about 10 years ago
b) I should have FIRST gone through a couple of decent JavaEE books and THEN read this (I ended up doing so anyway, at the cost of huge levels of frustration)
FLAWS IN THE BOOK
1 - There is no real clear distinction between JavaEE and Spring (Many Spring features have found their way into JavaEE 6 and 7, actually decreasing the importance of Spring itself... an option one would want to know when developing a Spring-based architecture)
2 - The example code has errors that would waste a (Spring) novice's time. It does not have a neat git repository via which one can simply download and import the code via Maven. That simple step would have saved me a lot of time
3 - I had a lot of problems with Spring errors, this book barely mentions anything about interpreting errors. I had to revert to Google to PAINFULLY find my way through them
4 - This book does not mention any of the limitations of Spring JPA when using non-relational repositories. A huge miss IMO. And anyone wanting to write a decent, modern Big Data/NoSQL server app should understand its implications (before trying to design the repository). Also no mention of Spring's over-engineering on many fronts (a good standard being over-applied).
5- Finally, this is a huge book, but does not cover most advanced topics.
- As a JavaEE novice, FIRST understand JavaEE (esp 6 & 7), THEN read this book and FINALLY determine if you really need Spring
- As a Spring novice, this book is the best of a bad lot (of Spring 3 books). Useful, but painful
- As a Spring (version 2) Pro, you do not need this book. The spring website is more than enough
(In any case, before you implement your system, please read the excellent book 'Spring Data' by Mark Pollack for the most appropriate data repository)
My other complaint is that I have submitted numerous errata to the publisher, but the publisher has not posted any of them on their errata site.
If you you're an experienced developer and are looking at learning Spring or already know Spring but want to get updated on 3.1, I highly recommend this book.
good => you learn about many distinct features.
bad => it's a little frustating when you finish a chapter of a technical book realizing you have so many questions that you need to find others sources of information to be confident.
Example: in the Transaction Manager chapter, the author do not even explain basic questions that are essential to properly design a system like:
- what makes Spring detect that a transaction is finished and then it is time to perform a commit?
- what makes Spring detect that a rollback is needed? May the application code mess this up if the code has, for instance, a catch block that handles an exception in the middle of the transaction stack?
In the end, I recommend the book, but for the ones that have in mind the assumption I wrote in the beginning: an overview of a lot of things.
Look for similar items by category
- Books > Computers & Technology > Programming > Java
- Books > Computers & Technology > Programming > Languages & Tools
- Books > Computers & Technology > Programming > Software Design, Testing & Engineering > Software Development
- Books > Textbooks > Computer Science & Information Systems > Computer Science
- Books > Textbooks > Computer Science & Information Systems > Programming Languages
- Books > Textbooks > Computer Science & Information Systems > Software Design & Engineering