- Paperback: 456 pages
- Publisher: Manning Publications; 1 edition (February 2, 2006)
- Language: English
- ISBN-10: 1932394583
- ISBN-13: 978-1932394580
- Product Dimensions: 7.5 x 1.3 x 9.5 inches
- Shipping Weight: 2.5 pounds (View shipping rates and policies)
- Average Customer Review: 32 customer reviews
- Amazon Best Sellers Rank: #1,738,343 in Books (See Top 100 in Books)
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.
POJOs in Action: Developing Enterprise Applications with Lightweight Frameworks 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
All Books, All the Time
Read author interviews, book reviews, editors picks, and more at the Amazon Book Review. Read it now
Customers who bought this item also bought
What other items do customers buy after viewing this item?
A solid, valuable and easy-to-read work. -- JavaRanch
About the Author
Chris Richardson is a developer, architect and mentor with over 20 years of experience. He runs a consulting company that jumpstarts new development projects and helps teams that are frustrated with enterprise Java become more productive and successful. Chris has been a technical leader at a variety of companies including Insignia Solutions and BEA Systems. Chris holds a MA & BA in Computer Science from the University of Cambridge in England. He lives in Oakland, CA.
Top customer reviews
As a tech lead, I even got copies of this book for new hires that were not versed in POJO or even web development. (Or even Java in one case!)
And while this book is completely practical it does the best job I have seen to give the pros and cons of each choice you can make with POJO, in a completely no-nonsense way. How refreshing! For instance, you can save objects to a database in 3 basic ways, each of which can either preserve the class hierarchy, save space, but possibly cost multiple table reads per object. It is up to you to choose what is important in your situation. Quick lists of trade-offs are all throughout this book.
I'm a little late to review this book, and Spring has gone on to add many more features (for instance lots of annotations to replace XML configuration files). However, I can't rate this book more highly and I still think it would make a great first book into POJOs, Spring, or web back-end web development.
It provides a brief introduction to the Spring Framework and Hibernate (as well as JDO), and covers at least enough material on each in order to demonstrate how to put both to use (together) in the example application that is used throughout the book. But it would be best to consult any of the numerous books and/or web resources that target those technologies specifically for more background and up-to-date implementation reference.
Other than a simple Servlet example in the Exposed Domain Model chapter, the book does not cover the Presentation layer - the focus is on the Business/Model layer.
Certainly the development framework landscape has changed and evolved since this book was published, but it's still a great practical resource which remains relevant in addressing important facets of application architecture that need to be considered and planned out.
That being said I think there are some excellent points the book brings out about the different Persistence layers and how debugging POJO's is so much easier than the alternatives.
The book is explains very good how to build enterprise apps using the pojo frameworks like spring, hibernate, jdo. It shows very nicely how to integrate these technologies. The code of the book is also awesome. It has a lot of examples.
Before reading this book I knew only hibernate. I saw the hard way that hibernate was not enough for building a complex project. So this made me to read this book. Reading this book I was forced to learn Spring too. When I tried to run the examples I saw that the examples project are built with Maven. I liked how simple and elegant the project was structured using Maven, so I learned Maven too(the book's code is an excellent example of Maven usage too).
I also saw that handling the concurrency in an (web) app is not an easy thing to do. The book has a good explanation of this topic in the last chapters. Chris is implementing some of the Fowler's patterns and that made me to get some more details about that so this is how I bought and read Fowler's book:Patterns of Enterprise Application Architecture which is by the way a excellent book too.
I highly recommend this book!
Good job Chris!
PS: too bad that I didn't have this book 2 years ago.