Niggle classes that wrap and extend the core Java Servlet API.
The class that will be of most concern to the application programmer is {@link com.revusky.niggle.servlet.ServletInteraction}, which represents the servicing of a single HTTP request. This abstract base class has various methods that are meant to be overridden by subclasses. The application programmer will create her own subclass with one or more execXXX methods that are the function entry points for the various actions that the servlet knows how to deal with.
Niggle provides its own subclass of javax.servlet.http.HttpServlet
,
{@link com.revusky.niggle.servlet.NiggleServlet}. This class
actually does very little, since it delegates its functionality to other objects.
For example, in response to a GET or POST request, it creates a new
{@link com.revusky.niggle.servlet.ServletInteraction ServletInteraction}
instance of the appropriate subclass. Initialization is delegated to an instanceof
{@link com.revusky.niggle.servlet.NiggleConfig com.revusky.niggle.servlet.NiggleConfig},
an object which sets up the various configuration details of a Niggle application,
such as the data registry and the location of the page templates. Under
most circumstances, this will be completely transparent to the application
programmer.