pageMap.xml 2.7 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566
  1. <!--
  2. Licensed Materials - Property of IBM
  3. IBM Cognos Products: mdsrv
  4. (C) Copyright IBM Corp. 2008, 2010
  5. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
  6. -->
  7. <!--
  8. Copyright (C) 2008 Cognos ULC, an IBM Company. All rights reserved.
  9. Cognos (R) is a trademark of Cognos ULC, (formerly Cognos Incorporated).
  10. -->
  11. <!--
  12. This is the DispatcherJSP framework pagemap file. The pagemap file has been SIGNIFICANTLY
  13. reduced in functionality from its original incarnation from CMM's ALP framework, this is inline
  14. with the single role of the DispatcherJSP framework, rendering JSP pages, no more no less.
  15. <br>
  16. This page map is referenced by the masterPageMap.xml. The masterPageMap.xml can reference one or
  17. more page map files, this provides for logical grouping of jsp pages which may be relevant to
  18. the application. An application may choose to use just a single page map file with all JSP's listed
  19. in that file.
  20. <br>
  21. The page map consists of a series of <page> tags. A page tag consists of the following
  22. <ol>
  23. <li>an id. This represents a page id (pid). This is a mandatory attribute</li>
  24. <li>A view attribute. This if present should refer to the package path of a jsp file, though not strictly necessary.
  25. The common useage is for this attribute to point at a jsp</li>
  26. <li>a '<custom></custom>' tag. This tag may be nested in the page element, it will be parsed and
  27. made available to the application hosting the dispatcherJSPDriver. The purpose of this tag is to
  28. allow an appliction to provide request attribtues in an HttpServletRequest, this can serve the
  29. purpose of a preinstantiated bean. The other useage is for an application to use the custom data
  30. to do it implement its own presentation service for a pid, which may render the output of the request
  31. in a manner other then JSP. The DispatcherJSP does NO processing of the custom section other then
  32. making it available for the application.
  33. -->
  34. <!-- It will help us if we keep the name attribute the same as the name of the file. -->
  35. <pageMap name="pageMap">
  36. <pages>
  37. <page id="lineageMain" view="/mdsrv/jsp/lineage/lineageMain.jsp">
  38. </page>
  39. <page id="error_pid" view="/mdsrv/jsp/error/error.jsp">
  40. </page>
  41. <page id="progress_pid" view="/mdsrv/jsp/progress/progress.jsp">
  42. </page>
  43. <page id="debug_pid" view="/mdsrv/jsp/debug/debug.jsp">
  44. </page>
  45. <page id="iis_pid" view="/mdsrv/jsp/iis/iis_redirect.jsp">
  46. </page>
  47. <page id="qf_fault_pid" view="/mdsrv/jsp/error/qf_fault.jsp">
  48. </page>
  49. <page id="pdm_process" view="/mdsrv/jsp/personalData/processData.jsp">
  50. </page>
  51. <page id="xml_dstream" view="/mdsrv/jsp/personalData/xmlDataStream.jsp">
  52. </page>
  53. </pages>
  54. </pageMap>