Author: mmcallis
Date: 2008-05-26 01:28:14 -0400 (Mon, 26 May 2008)
New Revision: 10815
Modified:
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/errorhandling.xml
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml
Log:
8.4. Handling Errors with JavaServer Pages (JSP)
- 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-05-25
14:42:48 UTC (rev 10814)
+++
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/errorhandling.xml 2008-05-26
05:28:14 UTC (rev 10815)
@@ -333,24 +333,21 @@
</para>
<para>
<note>
+ <title>Page property inheritance for objects</title>
<para>
- You can configure the page properties also on objects of type portal, in that case
they will be inherited by the pages
- which are located in the portal.
- </para>
- </note>
-</para>
-
- </sect2>
+ When page properties are configured for objects that use the
<emphasis>portal</emphasis> type, the properties are inherited by pages in
that portal.
+ </para>
+ </note>
+ </para>
+</sect2>
</sect1>
<sect1>
- <title>Handling errors with JSP</title>
- <para>As described above it is possible to redirect error handling to a
JavaServer Page. Two pages can be created
- to handle errors at portal and page level. Portal level error handling requires a
page that will produce a full
- page and the page level error handling requires a page that will produce markup for
a window only. When the page
- is invoked a set of request attributes will be passed.</para>
+ <title>Handling Errors with JavaServer Pages (JSP)</title>
<para>
+ As described in previous sections, error handling can be redirected to a JSP. 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
request attributes:
+ </para>
+ <para>
<table frame="all">
- <title>Request attributes</title>
<tgroup cols="3" align="left" colsep="1"
rowset="1">
<colspec colname='c1'/>
<colspec colname='c2'/>
Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml
===================================================================
---
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml 2008-05-25
14:42:48 UTC (rev 10814)
+++
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml 2008-05-26
05:28:14 UTC (rev 10815)
@@ -242,6 +242,7 @@
</para>
<para>
<note>
+ <title>Markup Fragments</title>
<para>
Portlets are responsible for generating markup fragments, as they are included on a
page and are
surrounded by other portlets. In particular, this means that a portlet outputting HTML
must