Rating: 
Summary: Ideal or Idolatry?
Review: If you are looking to learn from scratch, this is NOT the book for you. If you are an experienced programmer and can fill in the glaring voids in textual presentation, it can be a good reference.JSP is essentially ASP+ as the book was written before the announcement of ASP+, there is only one minor mention of it. It does present a contextual case for JSP and Beans (not EJB!). Beans are essentially components not unlike MS COM components or even OCX's. The good thing in the book is a REAL discussion of encapsulation of business logic as opposed to the other "pure" Bean books that prattle on and on with GUI stuff. The book suffers from being disjointed and has a distinctly academic flavor, but if you are experienced with Servlets or classes and know how to JAR and where to deploy, you will find it useful.
Rating: 
Summary: Trash Publishing - This Book Deserves 0 Stars
Review: Just as nine women cannot make a baby in one month, books such as this--written by committee--cannot possibly be well-written or coherent. This book is nearly 900 pages of horrible writing whose useful information could be recast into a well-written book of about 300 pages. For ample proof, check out the first 10-15 pages of chapter 15, which is mindless fluff written in a hurry. For example, here's what you'll learn about "physical security" on page 459: "The first step is to make sure that your machine(s) are physically secure. What this means is to physically protect the hardware and personnel that contain [sic] or run your machines. This can range from locks on your doors to armed guards or to James Bond-like biometric locks. ... [vapid paragraph mercifully omitted] When you think about physical security don't forget about laptops and palmtops. These machines are often the hardest to secure, and yet contain some of the most sensitive data about your organization. Passwords, social engineering information (such as information someone can use to fake their way past secretaries, etc.), or confidential plans may all be stored on those hard drives. A nefarious person or organization might use this data to break into your organization, to hatch their own plans based on your designs, improve their own product so they're much better than your weak points or may just use this information as a tool for bribery." And here I thought this was a book about JavaServer Pages, not a manual for idiots about securing machinery. Silly me. Before you click that Add to Shopping Cart button, take a long hard look at the quote above. At least half of this book is similar mindless drivel. Just say no to greedy publishers that round up a crew of programmers to rush a so-called book to market in order to get their grubby hands on your money. Remember, this book is authored by (no less than) 16 programmers. Would you hire 16 auto mechanics to lay the foundation of your new house? The programmers that wrote this book should leave writing to real authors. Whatever you do, don't forget to physically secure your laptops and palmtops.
Rating: 
Summary: Thumbs down
Review: Looks like a different author wrote each chapter, as much of the material is disjoined and lacks a logical flow.
Rating:
Summary: Thumbs down
Review: Looks like a different author wrote each chapter, as much of the material is disjoined and lacks a logical flow.
Rating: 
Summary: Great resource!
Review: Provides good coverage of many aspects of JSP. By utilizing the multi-author approach, the book draws on the expertise of many hands and gives the developer a broad perspective on writing and managing Java Server Pages. The book covers a wide range of topics and includes real world case studies of task you need to do on the job. Plenty of code examples, too.
Rating:
Summary: Overly verbose!
Review: The explanations are too wordy. Please be clear and to-the-point. I am a programmer, I need a JSP book that is clear, concise, and yet advance enough to help me reap the full benefits of JSP technology. This writting style seems to be the standard of this Stefan Zeiger et al group. Their last "red-covered" book which is "Professional Java Server Programming" is VERBOSE! Each book hit over 800 pages. Is that the goal? Well, the books are keeping me in shape. I am sorry guys. I am a terrible writer, myself. But when you produce a "Professional" book for programmers, please, put a 110% effort into it.
Rating:
Summary: Comprehensive
Review: The most comprehensive book I've ever read about JSP! Must have for JSP developer
Rating:
Summary: Not For Beginners, No Practical Use
Review: The title of my review sums it up. For a beginner I expected this book to get me up and running, It never did. I read the first 5 chapters and their was way too much focus on the Java code that was created by the JSP engine from a JSP page, and not enough emphasis on how to implement and use JSP. BOOOOH. And there are numerous spelling mistakes, including one on the first page of the introduction. C'mon WROX, wheres your QA/Copywriters? I will return this in exchange for ISBN 1884777996
Rating:
Summary: Not For Beginners, No Practical Use
Review: There are a lot of typos in this book. Worse than that, the examples are so long and detailed that it is very difficult to find particular pieces of information. For example, in the explanation of how JSPs interact with javaBeans, there is an excruciatingly detailed example of how to use JSPs, javaBeans, and JDBC. Not that JDBC is unimportant, but it introduces enough extra complexity should not be used to illustrate the above interaction. That being said, the necessary information is mostly there. Perhaps a future revision will be good once they've cleaned it up a bit.
Rating:
Summary: not clear
Review: There are a lot of typos in this book. Worse than that, the examples are so long and detailed that it is very difficult to find particular pieces of information. For example, in the explanation of how JSPs interact with javaBeans, there is an excruciatingly detailed example of how to use JSPs, javaBeans, and JDBC. Not that JDBC is unimportant, but it introduces enough extra complexity should not be used to illustrate the above interaction. That being said, the necessary information is mostly there. Perhaps a future revision will be good once they've cleaned it up a bit.
| 
