software design |
Aftersleep Books
|
||||||||||||||||||||
Programming Jakarta StrutsThe following report compares books using the SERCount Rating (base on the result count from the search engine). |
|||||||||||||||||||||
|
Aftersleep Books - 2005-06-20 07:00:00 | © Copyright 2004 - www.aftersleep.com () | sitemap | top |
1. The book is organized very poorly. For example, although throughout the book we've been seing ActionForms used in code, it's not until page 175 that we get "What Are ActionForms?" The IStorefrontService interface is finally described on page 158, even though it's been seen multiple times previously without any explanation as to what it is. On page 230, the author writes "I've mentioned the UserContainer and ApplicationContainer classes in previous chapters without defining exactly what they are." So the pattern is that things are just foisted upon the reader inside code listings with no explanation and no reference. Sometimes they are finally described hundreds of pages later, sometimes not. In-between are many pages of useful information, but that would have better been left for future chapters. We learn lots about how to extend Struts before we even know how the basics of it work. That makes no sense if you are looking for a tutorial. Needless to say, it's pretty confusing to look at stuff that isn't explained. Terrible.
2. There is no step-by-step creation of a working application here. I made the mistake of thinking there was by skimming the book, but the code is largely given in unconnected fragments, often without a reference to even what file it is supposed to go in (some code relates to no actual project at all). There are two applications presented (a bank account manager, and a shopping cart tool), but again it's almost impossible to create and configure what's in the book into working applications. Sure, you can download completed applications from a web site and try to decipher them on your own, but the fact that only bits and pieces of the code are in the book, with little or no methodology, is lazy.
To be fair, there are some pretty good chapters on ancillary topics, such as Business Objects and Object Persistence, Struts Tag Libraries, Tiles, and Logging. This information will be useful, but not before you can build a working Struts app to apply it to. I think it's a shame because with a little more thought from the user's perspective towards organization/editing, this could have been a really good book. If you already kind of know Struts, I would pick it up to augment your knowledge (perhaps in that instance I'd give it four stars), but I cannot recommend it for the Struts beginner. Sadly, I have not found a single Struts book or online tutorial yet that succinctly and sufficiently explains it to someone with no previous experience. I'm almost tempted to try the Tapestry framework instead...even though the documentation is horrible, the product looks easier to use.