Author: mmcallis Date: 2008-06-19 22:44:44 -0400 (Thu, 19 Jun 2008) New Revision: 11093 Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/errorhandling.xml Log: Chapter 8. Error Handling Configuration - period backup - minor revisions Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/errorhandling.xml =================================================================== --- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/errorhandling.xml 2008-06-19 19:34:09 UTC (rev 11092) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/errorhandling.xml 2008-06-20 02:44:44 UTC (rev 11093) @@ -193,7 +193,7 @@ </row> <row> <entry align="center"><computeroutput>control.portal.resource_uri</computeroutput></entry> - <entry align="center">the path of the JSP used for redirections</entry> + <entry align="center">the path to the JSP used for redirections</entry> <entry align="center">a valid path to a JSP located in the <filename>portal-core.war/</filename> directory</entry> </row> </tbody> @@ -201,7 +201,7 @@ </table> </para> <para> - The following portal configuration details the use of portal-policy properties: + The following portal configuration demonstrates the use of portal-policy properties: </para> <para> <programlisting><![CDATA[ @@ -286,7 +286,7 @@ </row> <row> <entry align="center"><computeroutput>control.page.resource_uri</computeroutput></entry> - <entry align="center">the path of the JSP used for redirections</entry> + <entry align="center">the path to the JSP used for redirections</entry> <entry align="center"><computeroutput>ignore</computeroutput>, <computeroutput>jsp</computeroutput> and <computeroutput>hide</computeroutput></entry> </row> </tbody> @@ -294,7 +294,7 @@ </table> </para> <para> - The following page configuration details the use of page-policy properties: + The following page configuration demonstrates the use of page-policy properties: </para> <para> <programlisting><![CDATA[ @@ -334,7 +334,7 @@ </para> <para> <note> - <title>Page property inheritance for objects</title> + <title>Page Property Inheritance for Objects</title> <para> When page properties are configured for objects that use the <emphasis>portal</emphasis> type, the properties are inherited by pages in that portal. </para> @@ -345,7 +345,7 @@ <sect1> <title>Using <trademark class="trade">JSP</trademark> to Handle Errors</title> <para> - As described in previous sections, error handling can be redirected to a <trademark class="trade">JSP</trademark>. Two pages can be created to handle errors, one for the portal level, and the other for the page level. Portal level error-handling requires a page that produces a full page, and page-level handling requires a page that produces markup, but only for a window. When the page is invoked, a set of request attributes are passed. The following table represents possible request attributes: + As described in previous sections, error handling can be redirected to a <trademark class="trade">JSP</trademark> page. Two pages can be created to handle errors: one for the portal level, and the other for the page level. Portal level error-handling requires a page that produces a full page, and page-level handling requires a page that produces markup, but only for a window. When the page is invoked, a set of request attributes are passed. The following table represents possible request attributes: </para> <para> <table frame="all"> @@ -412,7 +412,7 @@ </orderedlist> </para> <para> - The functionality is available as part of the properties for each configuration level. You can specify the default error handling policy (at the root of the portal object hierarchy) for each portal, or each page, by clicking on the <guibutton>Properties</guibutton> button for each page or portal: + Configuration options are available as part of the properties for each configuration level. You can specify the default error handling policy (at the root of the portal object hierarchy) for each portal, or each page, by clicking on the <guibutton>Properties</guibutton> button for each page or portal: </para> <para> <mediaobject>