|
18 of 18 people found the following review helpful:
4.0 out of 5 stars
Great book, makes it simple, October 11, 2002
This was a great book. It talks in great depth, not only about Struts, but also about J2EE in general. I would have called myself an upper-intermediate Java programmer when I picked up this book, but an a total newbie to J2EE. I put away my "Core Servlets and JavaServer Pages" (Hall) and "Enterprise JavaBeans (Monson-Haefel) books that were far too difficult to read in favor of this book's simple approach.It was AWESOME that he went through each and every one of the Struts JSP custom tags, describing their usage, and the attributes of each tag. I found this incredibly useful. I agreed that the examples in the book were real-world, and I found them effective in helping solidify my understanding. I was especially pleased with the time he spent on database access. This is documentation that is hard to find with Struts (and, frankly, with many Java application frameworks). But, there were some difficulties about the book that I didn't quite understand: 1. His database-access code is poorly written. He doesn't reuse any of the JDBC code. He isn't writing a book on a JDBC persistence layer API, I realize, but it made things difficult to follow as I focused on the code deficiences. An exercise for the reader to develop, I guess. 2. The code, as it is written in the book (and downloaded from the web site) doesn't execute without exceptions upon deployment to my JBoss container. If you're going to publish code in a book as an example, it really should compile and execute without modification. Otherwise, you should indicate that it doesn't execute unless you first do steps x, y, and z. 3. Chapter 5, on Views covers in good depth how to use the JSP pages as data gathering mechanisms (subheading "JSPs that Gather Data"), but doesn't cover AT ALL how to present that data. I guess he assumes we all know how to present it! In chapter 11, he covers how to use the <html:iterate/> custom tag to iterate over the result sets obtained from a database query, but there is no real detail in the book about it. I would imagine that 98% of us will be using this mechanism HEAVILY, and felt like it deserved a better treatment within chapter 5. 4. He didn't cover ANY of the M of MVC. He lumped all his JDBC code into his Action classes, which doesn't seem like good design to me. Also, it seemed like he made an assumption that Model = Database. This isn't exactly the case.
|