|
Art of Java Web Development Struts, Tapestry, Commons, Velocity, JUnit, Axis, Cocoon, InternetBeans, WebWork Neal Ford 2003 | 624 pages ISBN: 1932394060 |
|||
 |
$44.95 | Softbound print book | |
|
$22.50 | PDF ebook | |
Sample Chapters
Take a sneak peek at the book content in a PDF ebook chapter excerpt. You need Adobe's free Acrobat Reader software to view it. You may download Acrobat Reader here.
DESCRIPTION
A guide to the topics required for state of the art web development, this book covers wide-ranging topics, including a variety of web development frameworks and best practices. Beginning with coverage of the history of the architecture of web applications, highlighting the uses of the standard web API to create applications with increasingly sophisticated architectures, developers are led through a discussion on the development of industry accepted best practices for architecture.
Described is the history and evolution towards this architecture and the reasons that it is superior to previous efforts. Also provided is an overview of the most popular web application frameworks, covering their architecture and use. Numerous frameworks exist, but trying to evaluate them is difficult because their documentation stresses their advantages but hides their deficiencies. Here, the same application is built in six different frameworks, providing a way to perform an informed comparison. Also provided is an evaluation of the pros and cons of each framework to assist in making a decision or evaluating a framework on your own. Finally, best practices are covered, including sophisticated user interface techniques, intelligent caching and resource management, performance tuning, debugging, testing, and Web services.
WHAT THE READERS SAY ABOUT THIS BOOK...
"The Art of Web Development is one of the latest Manning books I've
purchased and I was amazed how well the problem was explained.
The same problem was solved at least 3 different ways so that the
difficulties of each solution could be clearly seen. It wasn't until chapter
4 that the final solution was realized. This was an excellent way of
making sure that the developer knew both what to do and WHY they
were doing it that way. Excellent."
-- Joshua Smith, a Reader