RefEntry Servlet Design

This chapter covers the servlet architecture and specifies interfaces. The servlet contains essentially everything necessary to serve up RefEntry documents inside a single WAR file. A first goal for a future version could be to solve the scalability problem presented when everything is included in the same WAR file, perhaps using an external data repository such as a database or a directory.

Figure 1. RefEntry Client and Servlet Together

The webman client viewer accesses the servlet through the servlet container. The servlet container takes responsibility for translating client browser requests into HttpServletRequest objects to the servlet, and for translating HttpServletResponse objects from the servlet into responses for the client browser. The servlet container also takes responsibility for managing several instances of the servlet to handle multiple threads.

Servlet Classes

Table of Contents
RefEntry — hold RefEntry document meta-information
RefEntryBackEnd — back end class holding RefEntry information
RefEntryIndex — index for searching RefEntry documents
RefEntryServlet — servlet class for webman client
RefEntryTransformer — transform RefEntry documents to XHTML

The following classes make up the servlet.