Overview | Package | Class | Tree | Deprecated | Index | Help
| Spring Framework
PREV CLASS NEXT CLASS | FRAMES NO FRAMES
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD

## org.springframework.web
Interface HttpRequestHandler

All Known Implementing Classes:
  BurlapServiceExporter, DefaultServletHttpRequestHandler, HessianServiceExporter, HttpInvokerServiceExporter, ResourceHttpRequestHandler

    public interface HttpRequestHandler

Plain handler interface for components that process HTTP requests, analogous to a Servlet. Only declares `ServletException` and `IOException`, to allow for usage within any `HttpServlet`}. This interface is essentially the direct equivalent of an HttpServlet, reduced to a central handle method.

The easiest way to expose an HttpRequestHandler bean in Spring style is to define it in Spring's root web application context and define an `HttpRequestHandlerServlet` in `web.xml`, pointing at the target HttpRequestHandler bean through its `servlet-name` which needs to match the target bean name.

Supported as a handler type within Spring's `DispatcherServlet`, being able to interact with the dispatcher's advanced mapping and interception facilities. This is the recommended way of exposing an HttpRequestHandler, while keeping the handler implementations free of direct dependencies on a DispatcherServlet environment.

Typically implemented to generate binary responses directly, with no separate view resource involved. This differentiates it from a `Controller` within Spring's Web MVC framework. The lack of a `ModelAndView` return value gives a clearer signature to callers other than the DispatcherServlet, indicating that there will never be a view to render.

As of Spring 2.0, Spring's HTTP-based remote exporters, such as `HttpInvokerServiceExporter` and `HessianServiceExporter`, implement this interface rather than the more extensive Controller interface, for minimal dependencies on Spring-specific web infrastructure.

Note that HttpRequestHandlers may optionally implement the `LastModified` interface, just like Controllers can, provided that they run within Spring's DispatcherServlet. However, this is usually not necessary, since HttpRequestHandlers typically only support POST requests to begin with. Alternatively, a handler may implement the "If-Modified-Since" HTTP header processing manually within its `handle` method.

Since:
  2.0
Author:
  Juergen Hoeller
See Also:
  `HttpRequestHandlerServlet`, `DispatcherServlet`, `ModelAndView`, `Controller`, `LastModified`, `HttpRequestHandlerAdapter`, `HttpInvokerServiceExporter`, `HessianServiceExporter`, `BurlapServiceExporter`

Method Summary
`void` | `handleRequest(javax.servlet.http.HttpServletRequest request, javax.servlet.http.HttpServletResponse response)` Process the given request, generating a response.

Method Detail

### handleRequest

    void handleRequest(javax.servlet.http.HttpServletRequest request,
                       javax.servlet.http.HttpServletResponse response)
                       throws javax.servlet.ServletException,
                              java.io.IOException

  Process the given request, generating a response.

  Parameters:
    `request` - current HTTP request
    `response` - current HTTP response
  Throws:
    `javax.servlet.ServletException` - in case of general errors
    `java.io.IOException` - in case of I/O errors

Overview | Package | Class | Tree | Deprecated | Index | Help
| Spring Framework
PREV CLASS NEXT CLASS | FRAMES NO FRAMES
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD