-New Riders Publishing
Product Details
Would you like to update product info or give feedback on images?
|
|
Share your thoughts with other customers:
|
||||||||||||||||||||||
|
Most Helpful Customer Reviews
14 of 14 people found the following review helpful:
1.0 out of 5 stars
A poor attempt at a case study,
By
This review is from: XML, XSLT, Java, and JSP: A Case Study in Developing a Web Application (Paperback)
There are some books that are published that you wonder why the publisher went through the exercise. New Riders should have rejected this manuscript. It claims to be a case study of XML, XSLT, and JSP but it isn't. It is a confused and confusing discussion of the author playing around with technology.The author wanted to try out some ideas so he decided to write a chat program. But there is no real design effort (you won't find a single UML diagram anywhere) so it is difficult to understand precisely what the application is supposed to look like. Without any real design, the application ends up with one servlet of over 50 pages and another of over 40 pages in length. (The book is inflated with 300 pages of source listings that are unreadable.) As a case study in how to do bad design and write awful code, the book can serve as a warning perhaps. As far as actually trying to explain any of this technology, the author admits that isn't the purpose of the book. In a case study you like to hear of problems encountered or the different solutions attempted but you won't. No mention is made of security or performance. The code itself is useless and can't be used in other applications because it is so poorly designed. The author admits that huge chunks of code need to be refactored. Overall this book fails to provide any real value.
13 of 14 people found the following review helpful:
1.0 out of 5 stars
not what I thought,
By Gerald McDonough (Minneapolis, MN United States) - See all my reviews
This review is from: XML, XSLT, Java, and JSP: A Case Study in Developing a Web Application (Paperback)
I bought this book hoping for an advanced and detailed comparison of 2 java server architectures: XML/XSLT versus JSP. It is not a comparison, or a tutorial, or an analysis of any kind. It is simply a meandering report of the author's experimention with miscellaneous technologies. No conclusions are reached. No pitfalls are described. Topics like performance and extensibility are not even touched. XSLT is only mentioned in passing as an approach that was not followed. XML is only discussed as an application's data store; a mildly interesting exercise that most certainly would not be used on any production web site. Lastly, over one third of the book is source code print out.
5 of 6 people found the following review helpful:
1.0 out of 5 stars
What a waste!,
By A Customer
This review is from: XML, XSLT, Java, and JSP: A Case Study in Developing a Web Application (Paperback)
Complete waste of money. I hate beating up authors, but this is nothing more than a dump of a software project from work. As such, there is little comparison-contrast, discussion of design choices, or benefit-pitfalls of the design. Don't expect to extract information from this text to apply to your own projects.I feel the publisher should put this book in a "out of print" status to save customer heartache. Did New Riders even review this book before releasing?
Share your thoughts with other customers: Create your own review
|
|
Tag this product(What's this?)Think of a tag as a keyword or label you consider is strongly related to this product.
Tags will help all customers organize and find favorite items. |