[jboss-cvs] JBossAS SVN: r104663 - projects/docs/enterprise/EWP_5.0.1/Seam_Reference_Guide/en-US.

[jboss-cvs-commits at lists.jboss.org]

Author: laubai
Date: 2010-05-11 02:23:27 -0400 (Tue, 11 May 2010)
New Revision: 104663

Modified:
   projects/docs/enterprise/EWP_5.0.1/Seam_Reference_Guide/en-US/Webservices.xml
Log:
Corrected tag issue.

Modified: projects/docs/enterprise/EWP_5.0.1/Seam_Reference_Guide/en-US/Webservices.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0.1/Seam_Reference_Guide/en-US/Webservices.xml	2010-05-11 06:19:48 UTC (rev 104662)
+++ projects/docs/enterprise/EWP_5.0.1/Seam_Reference_Guide/en-US/Webservices.xml	2010-05-11 06:23:27 UTC (rev 104663)
@@ -384,7 +384,7 @@
 				You do not have to send a HTTP error to the client if an exception occurs. Seam lets you map the exception as a redirect to a view of your Seam application. Since this feature is typically used for human clients (web browsers) and not for REST API remote clients, you should pay attention to conflicting exception mappings in <filename>pages.xml</filename>.
 			</para>
 			 <para>
-				The HTTP response does pass through the servlet container, so an additional mapping may apply if you have <literal><error-page></literal> mappings in your <literal>web.xml</literal> configuration. The HTTP status code would then be mapped to a rendered HTML error page with status <literal>200 OK</literal>.
+				The HTTP response does pass through the servlet container, so an additional mapping may apply if you have <literal>&lt;error-page&gt;</literal> mappings in your <literal>web.xml</literal> configuration. The HTTP status code would then be mapped to a rendered HTML error page with status <literal>200 OK</literal>.
 			</para>
 		</section>