123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566 |
- <!--
- Licensed Materials - Property of IBM
- IBM Cognos Products: mdsrv
- (C) Copyright IBM Corp. 2008, 2010
- US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
- -->
- <!--
- Copyright (C) 2008 Cognos ULC, an IBM Company. All rights reserved.
- Cognos (R) is a trademark of Cognos ULC, (formerly Cognos Incorporated).
- -->
- <!--
- This is the DispatcherJSP framework pagemap file. The pagemap file has been SIGNIFICANTLY
- reduced in functionality from its original incarnation from CMM's ALP framework, this is inline
- with the single role of the DispatcherJSP framework, rendering JSP pages, no more no less.
- <br>
- This page map is referenced by the masterPageMap.xml. The masterPageMap.xml can reference one or
- more page map files, this provides for logical grouping of jsp pages which may be relevant to
- the application. An application may choose to use just a single page map file with all JSP's listed
- in that file.
- <br>
- The page map consists of a series of <page> tags. A page tag consists of the following
- <ol>
- <li>an id. This represents a page id (pid). This is a mandatory attribute</li>
- <li>A view attribute. This if present should refer to the package path of a jsp file, though not strictly necessary.
- The common useage is for this attribute to point at a jsp</li>
- <li>a '<custom></custom>' tag. This tag may be nested in the page element, it will be parsed and
- made available to the application hosting the dispatcherJSPDriver. The purpose of this tag is to
- allow an appliction to provide request attribtues in an HttpServletRequest, this can serve the
- purpose of a preinstantiated bean. The other useage is for an application to use the custom data
- to do it implement its own presentation service for a pid, which may render the output of the request
- in a manner other then JSP. The DispatcherJSP does NO processing of the custom section other then
- making it available for the application.
- -->
- <!-- It will help us if we keep the name attribute the same as the name of the file. -->
- <pageMap name="pageMap">
- <pages>
- <page id="lineageMain" view="/mdsrv/jsp/lineage/lineageMain.jsp">
- </page>
- <page id="error_pid" view="/mdsrv/jsp/error/error.jsp">
- </page>
- <page id="progress_pid" view="/mdsrv/jsp/progress/progress.jsp">
- </page>
- <page id="debug_pid" view="/mdsrv/jsp/debug/debug.jsp">
- </page>
- <page id="iis_pid" view="/mdsrv/jsp/iis/iis_redirect.jsp">
- </page>
- <page id="qf_fault_pid" view="/mdsrv/jsp/error/qf_fault.jsp">
- </page>
- <page id="pdm_process" view="/mdsrv/jsp/personalData/processData.jsp">
- </page>
- <page id="xml_dstream" view="/mdsrv/jsp/personalData/xmlDataStream.jsp">
- </page>
- </pages>
- </pageMap>
|