[seam-commits] Seam SVN: r9667 - trunk/doc/Seam_Reference_Guide/en-US.

[seam-commits at lists.jboss.org]

Author: dan.j.allen
Date: 2008-11-27 00:48:13 -0500 (Thu, 27 Nov 2008)
New Revision: 9667

Modified:
   trunk/doc/Seam_Reference_Guide/en-US/Security.xml
Log:
fix validation errors in XML document


Modified: trunk/doc/Seam_Reference_Guide/en-US/Security.xml
===================================================================
--- trunk/doc/Seam_Reference_Guide/en-US/Security.xml	2008-11-26 20:49:02 UTC (rev 9666)
+++ trunk/doc/Seam_Reference_Guide/en-US/Security.xml	2008-11-27 05:48:13 UTC (rev 9667)
@@ -91,8 +91,10 @@
       <title>Configuring an Authenticator component</title>
 
       <note>
-        If you use Seam's Identity Management features (discussed later in this chapter) then it is not necessary to create
-        an authenticator component (and you can skip this section).
+        <para>
+          If you use Seam's Identity Management features (discussed later in this chapter) then it is not necessary to create
+          an authenticator component (and you can skip this section).
+        </para>
       </note>
 
       <para>
@@ -3220,7 +3222,6 @@
           A <literal>ResolverChain</literal> contains an ordered list of <literal>PermissionResolver</literal>s, for the
           purpose of resolving object permissions for a particular object class or permission target.
         </para>
-      </sect3>
       
       <para>
         The following sequence diagram shows the interaction between the components of the permission framework during a
@@ -3274,6 +3275,7 @@
           </para>
         </listitem>      
       </itemizedlist>
+      </sect3>
       
     </sect2>
 
@@ -4994,9 +4996,11 @@
 }]]></programlisting>
 
     <warning>
-      Note that an <literal>Identity</literal> component must be marked <literal>@Startup</literal>, so
-      that it is available immediately after the <literal>SESSION</literal> context begins.
-      Failing to do this may render certain Seam functionality inoperable in your application.
+      <para>
+        Note that an <literal>Identity</literal> component must be marked <literal>@Startup</literal>, so that it is
+        available immediately after the <literal>SESSION</literal> context begins.  Failing to do this may render
+        certain Seam functionality inoperable in your application.
+      </para>
     </warning>