Page lists
Page lists allow one to avoid hard-coding URLs in servlets and JSPs by specifying the location where a request is to be forwarded depending on the MIME type of the servlet.
For a given MIME type, specify a set of pages to invoke.
The PageListServlet custom extension is deprecated in WAS V7.0 and will be removed in a future release.
Re-architect legacy applications to use the Servlet 2.3 javax.servlet.filter classes, which can...
- Intercept requests and examine responses
- Achieve chaining functionality
- Embellish or truance responses
The following list of classes are deprecated:
- com.ibm.servlet.ClientList
- com.ibm.servlet.ClientListElement
- com.ibm.servlet.MLNotFoundException
- com.ibm.servlet.PageListServlet
- com.ibm.servlet.PageNotFoundException
WAS supplies PageListServlet, which is used to call a JSP file by name based on the configuration data in client_types.xml, whcih maps a JSP file to a 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 the servlets.
We can also logically group page lists according to the markup language type, such as, HTML or WML, allowing applications that use servlets to extend the PageListServlet servlet, to call JSPs which return the proper markup-language type for the client request. For example, a request that originates from a PDA device requires WML data. The appserver sends the request to a servlet that extends the PageListServlet servlet, and the servlet calls a JSP file that returns a WML response.
Related tasks
Set page list servlet client configurations
Related
Client type detection support
client_types.xml
Web apps: Links