Book Image

Tomcat 6 Developer's Guide

Book Image

Tomcat 6 Developer's Guide

Overview of this book

While Tomcat is one of the most popular servlet containers, its inner workings still remain a mystery to many developers. If you only have a superficial familiarity of how this container actually functions, much of its power remains untapped and underutilized. This book will provide you with all that you need to undertand how to effectively use Apache Tomcat. This book begins by providing detailed instructions on building a Tomcat distribution. The next few chapters introduce you to the conceptual underpinnings of web servers, the Java EE and servlet specifications, and the Tomcat container. Subsequent chapters address the key Tomcat components, taking care to provide you with the information needed to understand the internal workings of each component. Detailed examples let you walk through a Tomcat installation, stepping into key Tomcat components, as well as into your own custom servlets. During the course of the book you will encounter various structural components such as the Server and Service; containers such as the Engine, Host, Context, and Wrapper; and helpers such as the Loader, Manager, and Valve. You will also see how Tomcat implements the JNDI API to provide both a directory service for storage agnostic access to its resources, as well as a naming service that implements the Java EE Environment Naming Context. Along the way you will learn how various elements of the servlet 2.5 specification, as well as the HTTP RFCs are implemented by a servlet container. By the end of your journey, you will be able to count yourself as part of the elite minority of Java EE web developers who truly understand what goes on under the covers of a servlet container.
Table of Contents (17 chapters)
Tomcat 6 Developer's Guide
Credits
About the author
Acknowledgement
About the reviewers
Preface

Hot deploying a context


The reloadable attribute of a context indicates that resources should be watched for modification and that a reload of the context should be triggered if an application's resources have been modified.

Note

While reloading a context is invaluable during development, it requires significant runtime overhead and so should be left turned off in a production environment.

Determining if a reload is necessary

As we saw in the last chapter, a context may be reloaded when a watched resource is modified or deleted. In addition, a key responsibility of a WebappLoader is to provide a backgroundProcess() method implementation that is called by its parent container's background processing thread. Note that this method is of use only for a context whose reloadable attribute is set to true.

This method delegates to its WebappClassLoader instance, which checks each class or resource name in the paths array to see whether it has been modified since it was last accessed, by comparing its...