40 lines
2.9 KiB
HTML
40 lines
2.9 KiB
HTML
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||
|
|
<html>
|
||
|
|
<head>
|
||
|
|
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
|
||
|
|
<LINK rel="stylesheet" type="text/css" href="../../../rzahg/ic.css">
|
||
|
|
|
||
|
|
<title>Page lists</title>
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<BODY>
|
||
|
|
<!-- Java sync-link -->
|
||
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
||
|
|
|
||
|
|
<h4><a name="servpage"></a>Page lists</h4>
|
||
|
|
|
||
|
|
<p>Page lists allow you to avoid hardcoding Uniform Resource Locators (URLs) in servlets and JavaServer Pages (JSP) files. A page list specifies the location where a request is to be forwarded, but automatically tailors that location depending on the MIME type of the servlet. These properties allow you to specify a markup language and an associated MIME type. For the given MIME type, you also specify a set of pages to invoke.</p>
|
||
|
|
|
||
|
|
<p>WebSphere Application Server - Express supplies the PageListServlet, which you can use to call a JSP file by name based on the configuration data in the client_types.xml file. This file maps a JSP file to a Uniform Resource Identifier (URI). When the URI is invoked, it specifies another JSP file in a Web module. This support allows you to access multiple URLs without hard-coding them in your servlets.</p>
|
||
|
|
|
||
|
|
<p>You can also logically group page lists according to the markup language type, as for example, HTML or Wireless Markup Language (WML). This allows applications, using servlets that extend the PageListServlet, to call JSP files that return the proper markup-language type for the client request. For example, if a request originates from a PDA device that requires WML data and is sent to a servlet that extends the PageListServlet, the servlet can call a JSP file that returns a WML response.</p>
|
||
|
|
|
||
|
|
<p>You can define PageListServlet configuration information in the IBM Web Extensions file. The IBM Web Extensions file is created and stored in the Web Applications archive (WAR) file.</p>
|
||
|
|
|
||
|
|
<p>In addition to providing the page list mapping capability, the PageListServlet also provides Client Type Detection support. A servlet determines the markup language type that a calling client needs in the response, using the configuration information in the client_types.xml file. For more information, see <a href="servpxml.htm">client_types.xml</a>.</p>
|
||
|
|
|
||
|
|
<p>Client type detection support allows a servlet, extending the PageListServlet, to call an appropriate JSP file. The servlet invokes the callPage() method, which calls a JSP file based on the markup-language type of the request.</p>
|
||
|
|
|
||
|
|
|
||
|
|
<blockquote>
|
||
|
|
<p><strong><a href="servpex.htm">Example: Extending PageListServlet</a></strong>
|
||
|
|
<br>See this topic for an example of how to extend the PageListServlet class.</p>
|
||
|
|
|
||
|
|
<!--<p><strong><a href="servpcfg.htm">Configure and implement page lists</a></strong>
|
||
|
|
<br>This topic contains information on page lists.</p>-->
|
||
|
|
</blockquote>
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|
||
|
|
|