Very inconsistent from chapter to chapter

Some of the chapters in this I found very useful e.g. class loaders, and some I found to be very bad e.g. JDBC. It seems that the book really needed to have someone not familiar with the subject matter give it a review as it was very common to mention a concept several times in a paragraph that had not been explained previously in the book/chapter. In at least one case the object was not explained until several chapters further into the book. Some sections at least reference that an explanation is forthcoming in the next few pages and that allows to reader to just wait fort hat to come.

Some of the call-out tables are completely pointless, e.g. they `explain' all the possible arguments ends up reading like "switch -allow_JDBC description - allows access to JDBC". If you can add no value beyond the switch name, why waste the paper.

The security chapter says it is a perfectly secure practice to give developers read only access to production databases; statements like this should be qualified to reference the type of data that is being stored.
If the SysAdmins of Amazon followed these practices and my name, address, credit card, password etc. were available to the entire organization I would not be pleased. I am sure that is not the case with Amazon as that would be an issue for SOX as well as PCI.

I am about 2/3rds of the way through the book now, and if I had known it would be this bad I would have abandoned it earlier, I am now far enough in that I do not think it is worth starting fresh with an O'Reily book.

This book gets two stars from me as I had some real `a-haaaa' moments reading it, my issues is many of the chapters feel like they were shoved in without proper care, and certainly without a proper independent review.

I have now descended to scrawling notes on the book at the pieces that are clearly incorrect, items that say something can be done three ways without discussing the benefits / risks of each, tables / diagrams that do not match the text used to explain them, and the grammatical errors.

I am not a nit-picking person, I am sure my review is full of grammatical, spelling issues etc., but the point of a text book is you pay close attention while trying to commit these things to your brain, and the number of errors in the last couple of chapters I have been reading are such that I can not stay focused on the material.

This book gives a speedstart in getting high level architecture of Tomcat 5. Its discussion, even though not comprehensive, can make you can tell the difference between a valve, a service, an instance, and a server.



However, this book fails to provide a tested and consistent example on setting up DBCP (Apache Database Connection Pooling). Seems the information was extracted only from Apache DBCP website and reworded (such as replacing jndi/myoracle to jndi/wroxTC5) WITHOUT giving actual tested examples. I have Tomcat 5.0.28 running and the DBCP example mentioned 3 pages in chapter 8 and another 3 pages in chapter 14 does not work. I went looking for errata in the website but couldnt find it in the publisher's website.



It is rather disappointing and discouraging when you put your trust to a book that in the end gives bad examples.

This book gives a speedstart in getting high level architecture of Tomcat 5. Its discussion, even though not comprehensive, can make you can tell the difference between a valve, a service, an instance, and a server.

However, this book fails to provide a tested and consistent example on setting up DBCP (Apache Database Connection Pooling). Seems the information was extracted only from Apache DBCP website and reworded (such as replacing jndi/myoracle to jndi/wroxTC5) WITHOUT giving actual tested examples. I have Tomcat 5.0.28 running and the DBCP example mentioned 3 pages in chapter 8 and another 3 pages in chapter 14 does not work. I went looking for errata in the website but couldnt find it in the publisher's website.

It is rather disappointing and discouraging when you put your trust to a book that in the end gives bad examples.

This book contains some good information. However, it's clear that the publisher merely solicited a bunch of articles and sort of threw them together without much in the way of an overarching design. The result is that you can find answers to many common Tomcat questions in this book, but others will go unanswered.

I agree with the previous comments that this book has some major gaps in its coverage of the topic. I would also comment that some of the presentation is pretty confusing, such as the whole area of data source configuration, which is actualy covered TWICE. Which section of the book where it's covered are you supposed to follow? And, as it turns out, even though this subtopic is covered twice, they still don't manage to give a complete explanation, leaving out the important issue of setting up a context.xml file.

It's better than not having any Tomcat book at all, but this is not an exceptionally complete or well-organized book.

This book contains some good information. However, it's clear that the publisher merely solicited a bunch of articles and sort of threw them together without much in the way of an overarching design. The result is that you can find answers to many common Tomcat questions in this book, but others will go unanswered.

I agree with the previous comments that this book has some major gaps in its coverage of the topic. I would also comment that some of the presentation is pretty confusing, such as the whole area of data source configuration, which is actualy covered TWICE. Which section of the book where it's covered are you supposed to follow? And, as it turns out, even though this subtopic is covered twice, they still don't manage to give a complete explanation, leaving out the important issue of setting up a context.xml file.

It's better than not having any Tomcat book at all, but this is not an exceptionally complete or well-organized book.

Very good book, but I first read it as a preparation to manage a tomcat server and I could barely understand. A re-read it later on and it was a lot clearer.

I looked through it in 1 day, from the programmer point of view, what I learned is totally worth I paid for the book, I have a clear overall picture of Tomcat, the components ( server, service, host,contexs),directories,especially the class loaders that helps me develop my web applications.
if you are just a programmer and a looking for some systematic inforation of Tomcat, you just need read 3 or chapters,probably this information is publiclly available in tomcat's offical website. this is why I finished in just 1 day.

as a beginner to the world of Java, Servlets, and JSP, this provided the best introductory place to begin learning these technologies.

More so than any of the o'reilly books, this volume takes you through the necessary introductory concepts. The examples are simple but not trivial, and present material in a way that can be readily absorbed and reused.

This is not a reference book- I feel comfortable setting it aside now that I have digested the contents. But, having been lost in a maze of other reference volumes from Learning Java (too trivial and slow-paced) to JSP Cookbook (too difficult to start) this provides the healthy, learn-quick but absorb-as-well volume I needed.

There is a lot of good information in this book, and it's true that it gets into JMX, the web-based manager and admin apps, etc., etc.

But I have some real concerns with this book. Here are four everyday "real world" tasks that a professional really needs to know and that one is hard-pressed to find accurately and succinctly discussioned in this book: (1) JVM memory settings -- in what file to set them; (2) How to pre-compile JSPs so that they are not compiled "on the fly" after deployment (absolutely crucial for the real world); (3) how to define a context.xml file and put it in your app's META-INF directory; (4) How to get an app deployed to the root.

I hope the authors can address these issues in the next edition.

Here's some more detail on these issues:

(1) Memory settings: p. 417: Gives switches for memory optimization, but doesn't say what is the best file in the Tomcat deployment for updating such settings. (The info in "Shared Tomcat Hosting," pp. 392-393, doesn't help for the easy case.) There is no discussion that if you use the Windows Service, the memory settings are set through the "Configure Tomcat" GUI application (and catalina.bat isn't used). A *general* item for "memory settings" is not listed in the index under JVM.

(2) How to pre-compile JSPs: Nothing. A better book would provide a working ant target for this. jspc (and/or org.apache.jasper.JspC) isn't even in the index.

(3) How to use a context.xml file and put it in your web-app's META-INF: Nothing. This is incredibly important because it's how you would define a DataSource without having to meddle with the server.xml file.

(4) How to get an app deployed to the root path. While there is some discussion of the root (e.g., p. 92), I don't see anything that points out the crucial piece of information, which is that the .war must be named ROOT.war (you can deploy another .war to the root, but with some settings it won't get redeployed properly after a fresh startup).

-----

I also wish the discussion of the JK and JK2 connectors was more complete. The discussion of the internals are interesting, but you would never learn about the no-jk environment variable (crucial for getting Apache to skip JK for certain paths) for JK. And if there is such a feature for JK2 (I don't think there is), you'd never find it here.

In short, I keep this near my desk, but I probably wouldn't recommend it to someone.

Good book, no fluff..just stuff. Explains diff. between 4.0 and 5.0, gives latest cofig and development tech for 5.0

Development of the Apache project's Tomcat JSP and Servlet engine continues apace, and again, Wrox has done a good job in swiftly getting a book to market which covers the latest version.

Wrox's earlier book by many of the same authors, 'Professional Apache Tomcat' covered versions 3 and 4. This book no longer contains any material specific to version 3, but has had a major overhaul and concentrates on Tomcat 5, though it's still useful and relevant to administrators working with version 4.1 and up.

Like its predecessor, the book covers the installation and management of Tomcat in great depth on both Unix and Windows. Its Unix coverage is geared towards Linux in favour of any other version of Unix, but in practice there's nothing particularly Linux specific and users of other Unix variants will have no problems following the examples.

As with the previous edition, the first two chapters provide background to the Apache project, J2EE and the evolution of web application technologies from CGI to JSP. Detailed chapters on installation and architecture follow. Only installation of the Tomcat binaries is here though; building Tomcat from source with Ant is not discussed at all (however, Ant is referred to throughout the book, mainly in relation to application building and deployment, and gets an appendix of its own). The architecture description is unchanged from the previous edition, but remains an excellent overview of Tomcat's internal components.

And on to the nuts and bolts. A lot of space is given to the new web-based administration tool (itself a web application handled by Tomcat), but at all points the underlying affects on Tomcat's raw XML configuration files is made clear, so the command line junkies - or those who choose not to enable the Administration Tool at all - are catered for in parallel with the point-and-click brigade. Web application configuration and management is much expanded, now covering Servlet 2.4 descriptors as well as those for 2.3.

Tomcat's HTTP connectors, employed when Tomcat is set up as a stand alone web and application server are described in a single chapter, but new to this book are details of using the SSI and CGI servlets which are new features of Tomcat 4.x and 5.

For non-trivial installations, one would wish to integrate Tomcat with a web server, creating an environment in which the web server delegates dynamic content to Tomcat which otherwise no longer handles HTTP directly. There are a number of protocols available for Tomcat which provide the connection to a web server. As these protocols have stabilised in Tomcat, so the book no longer covers the older, largely deprecated connectors beyond a brief description of each. It then concentrates almost solely on the JK2 implementation of AJP.

This whole area is a lot clearer than it was in the earlier book: a short chapter provides the background and describes the protocols used to connect the web server and Tomcat, followed by a chapter devoted to each of Apache (for both Unix and Windows) and Microsoft's IIS web server using the JK2 connector. I was a little disappointed to find that Sun's web server gets no mention at all, particularly as up-to-date official documentation in relation to it appears to be non-existent. Nonetheless, what's here for Apache and IIS is very good; Apache users get a better deal than their IIS counterparts though - the load balancing and SSL integration sections are far more complete in the IIS chapter.

That completes the first half of the book, and for many uses will provide more than enough information to get a good understanding of Tomcat and a working service. Six more chapters go into great detail about Tomcat's other features. Separate chapters exploring JDBC connectivity, the new JMX features of version 5 and Java class loaders really earns the book its Professional tag. Arguably more useful (in my case at least) are the chapters dedicated to security, clustering for fail-safe operation and embedding Tomcat within an application - absolutely everything is here. The chapter on server load testing proved to be a great help to me just for the inclusion of the use of JMeter, another Apache project which is useful for all manner of web server benchmarking.

Tomcat's documentation is more than adequate for quickly setting up a Tomcat server, but dig much deeper and it quickly becomes difficult to find what you're looking for. Having a book like this with everything to hand makes life a lot easier, and in any case it's worth much more than the official documentation.

Criticisms? I'd like to have seen an appendix or two giving a summary of the main Tomcat configuration files workers2.properties and server.xml; as it is not quite everything is covered and what is spread across different chapters. At the moment I'm working with Sun's web server and Tomcat and it would have been great to have a chapter dedicated to this particular setup, particularly as far as JK2 is concerned.

Wrox had some difficulties last year when its parent company collapsed, but now that Wiley have taken over, it's good to see them back on their feet and continuing to produce books like this, complete with their familiar red covers (...and dodgy author photographs). Highly recommended.