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

Mappers


A container uses the mapping rules defined by the servlet specification to map an incoming request URI to the appropriate context and servlet that will process the request.

In this section, we will explore these rules and then discover how this mapping is implemented within Tomcat.

Mapping rules

The target context is determined based on the longest context path on the URL that matches one of the contexts for the specified virtual host.

Once a successful context match has been found, the remainder of the URL, up to the query string, is considered for a match with the wrappers associated with that context. Each of the rules below is tried, in a case sensitive manner, until the first match is found, at which point the matched wrapper is returned.

  • Exact path matching: The servlet path on the request is checked for an exact match with the servlet path in the<servlet-mapping> element. An exact match pattern must start with a / and must not end with a /*. An example of an exact...