Most Helpful Customer Reviews
|
|
12 of 13 people found the following review helpful:
2.0 out of 5 stars
Welcome back to the 80's, May 31, 2006
This book seems to be a step backwards rather than a step forward. I may be a bit biased, since I feel that Object Oriented programming is much more beneficial than procedural, but this book harps on exposing all your "objects" (and I use this term lightly here) in order to utilize the frameworks. The book gave little hints as to why you would use some of these frameworks, but i'm hoping that a re-read may enlighten me (hibernate and tapestry I can understand, but the others are unclear to me in regards to his problem domain).
Regarding design and research, this book begins strongly by stating it should be done, and then skips it entirely. It then dives straight into utilizing hibernate, which is a good product if used properly, and then forces you to create data containers with access to all your data. From here you can get a feel as to the next few chapters and their structures; pushing data here, pushing data there.
In the end, I wondered if the book was at all useful in my persuit in finding a better way in working with J2EE-ish frameworks and an alternate solution to its heavy-ness, and in doing so offering an OO solution. This book failed miserably in doing so. I get the idea of JBoss being a lightweight solution, but he states that lightweight is about your coding style and the amount of work needing to be done. His project is grossly complex and would thus require a nightmare of work in maintenance as well as re-engineering when the time came (which it almost always will, especially when developing web based services).
It's possible that I'm alone in this view, but it seems that many developers think that the more advanced frameworks they pull together into a single project the better it becomes. In such, the frameworks used gauges the success of you project. It's about how good the product is and how easily it can be maintained, not by the number of frameworks you can integrate.
In the end, the book enlightened me to other frameworks, and possible ways of NOT using them. The author may have many years of experience, but I feel that this book brings a false hope in building better web-based applications, especially in regard to ongoing maintenance.
|
|
|
10 of 11 people found the following review helpful:
4.0 out of 5 stars
"Plain" dealing, March 24, 2006
Missourians -- residents of the "Show Me State" -- are sure to appreciate this unusual book on lightweight Java development with "Plain Old Java Objects." In a fast-paced 10 chapters, Brian Sam-Bodden builds a single complete application, all the way through. Believe it or else, he starts with a detailed design, then talks about fundamental tools like Eclipse and Ant, and before you know it he's implemented the persistence and business tiers. Screenshots and detailed instructions will help you get your environment installed and set up in no time.
The first five chapters of the book are astonishingly linear as the application is developed to this point, with each technology choice presented as a fait accompli. In this day of political correctness and cultural relativism, many authors bend over backwards to consider all the alternatives to every decision they make, and I felt that Sam-Bodden's approach was incredibly refreshing. Eclipse, Ant, Hibernate, EJB3 on JBoss. Take it or leave it.
I was therefore almost disappointed when, in Chapters 6 and 7, he considers several different alternative implementations of the business and presentation tiers. Still, showing how to use Tapestry and especially Spring offsets the raised eyebrows some of you might have on hearing that a book on POJOs was advocating using EJBs -- even though the radically reworked EJB3 specification does indeed let you use Plain Old Java Objects to implement the business layer.
From this point, the book gets more conventional, with the traditional tacked-on chapter about testing that nevertheless asks you to do testing as an integral part of development.
Although some of the technology choices and development approaches may stretch your personal definition of the term "lightweight," this is still the best book on end-to-end development of modern enterprise applications that I've seen. If you have a hint of the Missourian in you, and you'd like someone to show you how things are done, this book was written with you in mind.
|
|
|
4 of 4 people found the following review helpful:
3.0 out of 5 stars
Well written but..., May 24, 2007
I like the style of the book but I found myself having to play around with code to get the examples to work. They seemed to work about 25% of the time without major tweaking. Maybe it is just me but this book needs a newer edition pronto. I'd look elsewhere for more up to date information.
|
|
|
Most Recent Customer Reviews
|