Author: mmcallis Date: 2008-06-02 02:48:33 -0400 (Mon, 02 Jun 2008) New Revision: 10897 Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/errorhandling.xml Log: Chapter 8. Error Handling Configuration - revisions. Still need to confirm changes... 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-02 05:32:16 UTC (rev 10896) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/errorhandling.xml 2008-06-02 06:48:33 UTC (rev 10897) @@ -37,7 +37,7 @@ </listitem> <listitem> <para> - <emphasis>Resource unavailable</emphasis>: the resource was found, but it is not serviceable. + <emphasis>Resource unavailable</emphasis>: the resource was found, but was not serviceable. </para> </listitem> </itemizedlist> @@ -118,13 +118,13 @@ <sect2> <title>Portal Policy</title> <para> - The portal error-policy controls the response sent to the Web browser when an error occurs. A default error policy exists, which can be configured per portal. If an error occurs, the policy can either handle a redirect to a JSP page, or ignore the error. If the error is ignored, it is handled by the default policy, otherwise a JSP page is invoked with the appropriate request attributes, allowing page customization. + The portal error-policy controls the response sent to the Web browser when an error occurs. A default error policy exists, which can be configured per portal. If an error occurs, the policy can either handle a redirect to a JSP page, or ignore it. If the error is ignored, it is handled by the default policy, otherwise a JSP page is invoked with the appropriate request attributes, allowing page customization. </para> </sect2> <sect2> <title>Page Policy</title> <para> - The window error-policy controls how pages react to aggregation errors. Most of the time, pages are an aggregation of several portlet windows, and the action to take when an error occurs differs from other policies. When an error occurs, the policy can either handle it, or ignore it. If the error is ignored, it is handled by the portal policy. Possible actions taken after such errors are: + The window error-policy controls how pages react to aggregation errors. Most of the time pages are an aggregation of several portlet windows, and the action to take when an error occurs differs from other policies. When an error occurs, the policy can either handle it, or ignore it. If the error is ignored, it is handled by the portal policy. Possible actions taken after such errors are: </para> <para> <itemizedlist> @@ -135,7 +135,7 @@ </listitem> <listitem> <para> - replace the markup of the window by a redirection to a JSP page. + replace the markup of the window using a redirection to a JSP page. </para> </listitem> </itemizedlist> @@ -406,13 +406,13 @@ </listitem> <listitem> <para> - Click the <guibutton>Admin</guibutton> button on the top right-hand of the welcome page. Four tabs will appear on the left-hand side of the screen. Click on the <guibutton>Admin</guibutton> tab to open the portal management application. + Click the <guibutton>Admin</guibutton> button on the top right-hand of the welcome page. Four tabs will appear on the left-hand side of the page. Click on the <guibutton>Admin</guibutton> tab to open the portal management application. </para> </listitem> </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 hierachy) for each portal. or each page by clicking on the <guibutton>Properties</guibutton> button for each of these pages or portals: + 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: </para> <para> <mediaobject>