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

Aspects of the Context component


The components that we have encountered up until now, such as the server, service, engine, and host, have tended to be far more interesting to administrators than to developers. It is with the context, however, that this balance begins to shift.

To serve this duality of purpose, a context actually exposes two forms of itself. To an administrator, it shows itself in its 'Context' aspect, whereas to a developer, it shows itself in its 'Web application' aspect.

Each aspect comes with its own set of configuration files; the context aspect of this component is configured using a context fragment, whereas a deployment descriptor is used to configure its web application aspect.

If that weren't exciting enough, each aspect can be configured at three separate levels at the server level, at the host level, and at the individual context level. This inheritance hierarchy helps you in organizing your configuration parameters. You can move general configuration to a higher...