Title: Can the examples be any more Confusing???
Product review: This book must have been rushed to market. Normally, I buy a tech book and count the examples to get me through the more complicated material. I find it easier to simply read the code sometimes vs spending my time reading what the author has to say. Well, with Struts Essentials that isn't an option. The examples are horribly confusing.For each sample app the author just used a naming scheme of chapter number and then he adds an incrementing number at the end of the chapter name to get the class/file name.The index page would be ch04_01.jsp. An Action class would be ch04_02.java. A form would be ch04_03.java. And a results jsp page would be ch04_04.jsp.What a bad idea. So then try to imagine learning how to tie the Struts concepts together with writing a struts-config.xml. It's very ugly and so very confusing.Insult to injury, I've found a number or errata but there isn't anywhere on the books site to let the author/publisher know.Buy a different book.
Would you say this review depicts the product in a flattering or unflattering light?
