Home | Download | PDF | API | FAQ | Search | Feedback | History

> ## Invoking Other Web Resources

> Web components can invoke other web resources in two ways: indirectly and directly. A web component indirectly invokes another web resource when it embeds a URL that points to another web component in content returned to a client. In the Duke's Bookstore application, most web components contain embedded URLs that point to other web components. For example, `ShowCartServlet` indirectly invokes the `CatalogServlet` through the embedded URL
> `/bookstore1/catalog`.

> A web component can also directly invoke another resource while it is executing. There are two possibilities: The web component can include the content of another resource, or it can forward a request to another resource.

> To invoke a resource available on the server that is running a web component, you must first obtain a `RequestDispatcher` object using the `getRequestDispatcher("URL")` method.

> You can get a `RequestDispatcher` object from either a request or the web context; however, the two methods have slightly different behavior. The method takes the path to the requested resource as an argument. A request can take a relative path (that is, one that does not begin with a `/`), but the web context requires an absolute path. If the resource is not available or if the server has not implemented a `RequestDispatcher` object for that type of resource, `getRequestDispatcher` will return null. Your servlet should be prepared to deal with this condition.

> ### Including Other Resources in the Response

> It is often useful to include another web resource--for example, banner content or copyright information--in the response returned from a web component. To include another resource, invoke the `include` method of a `RequestDispatcher` object:

>     include(request, response);

> If the resource is static, the `include` method enables programmatic server-side includes. If the resource is a web component, the effect of the method is to send the request to the included web component, execute the web component, and then include the result of the execution in the response from the containing servlet. An included web component has access to the request object, but it is limited in what it can do with the response object:

> - It can write to the body of the response and commit a response.
> - It cannot set headers or call any method (for example, `setCookie`) that affects the headers of the response.

> The banner for the Duke's Bookstore application is generated by `BannerServlet`. Note that both `doGet` and `doPost` are implemented because `BannerServlet` can be dispatched from either method in a calling servlet.

>     public class BannerServlet extends HttpServlet {
>       public void doGet (HttpServletRequest request,
>         HttpServletResponse response)
>         throws ServletException, IOException {
>           output(request, response);
>       }
>       public void doPost (HttpServletRequest request,
>         HttpServletResponse response)
>         throws ServletException, IOException {
>           output(request, response);
>     }

>     private void output(HttpServletRequest request,
>         HttpServletResponse response)
>         throws ServletException, IOException {
>         PrintWriter out = response.getWriter();
>         out.println("<body bgcolor=\"#ffffff\">" +
>         "<center>" + "<hr> <br> &nbsp;" + "<h1>" +
>         "<font size=\"+3\" color=\"#CC0066\">Duke's </font>" +
>         <img src=\"" + request.getContextPath() +
>         "/duke.books.gif\">" +
>         "<font size=\"+3\" color=\"black\">Bookstore</font>" +
>         "</h1>" + "</center>" + "<br> &nbsp; <hr> <br> ");
>       }
>     }

> Each servlet in the Duke's Bookstore application includes the result from `BannerServlet` using the following code:

>     RequestDispatcher dispatcher =
>       getServletContext().getRequestDispatcher("/banner");
>     if (dispatcher != null)
>       dispatcher.include(request, response);
>     }

> ### Transferring Control to Another Web Component

> In some applications, you might want to have one web component do preliminary processing of a request and have another component generate the response. For example, you might want to partially process a request and then transfer to another component depending on the nature of the request.

> To transfer control to another web component, you invoke the `forward` method of a `RequestDispatcher`. When a request is forwarded, the request URL is set to the path of the forwarded page. The original URI and its constituent parts are saved as request attributes `javax.servlet.forward.[request_uri|context-path|servlet_path|path_info|query_string]`. The `Dispatcher` servlet, used by a version of the Duke's Bookstore application described in The Example JSP Pages (page 196), saves the path information from the original URL, retrieves a `RequestDispatcher` from the request, and then forwards to the JSP page `template.jsp`.

>     public class Dispatcher extends HttpServlet {
>       public void doGet(HttpServletRequest request,
>         HttpServletResponse response) {
>         RequestDispatcher dispatcher = request.
>           getRequestDispatcher("/template.jsp");
>         if (dispatcher != null)
>           dispatcher.forward(request, response);
>       }
>       public void doPost(HttpServletRequest request,
>       ...
>     }

> The `forward` method should be used to give another resource responsibility for replying to the user. If you have already accessed a `ServletOutputStream` or `PrintWriter` object within the servlet, you cannot use this method; doing so throws an `IllegalStateException`.