[jboss-cvs] jboss-seam/doc/reference/en/modules ...

[Shane Bryzak]

  User: sbryzak2
  Date: 07/02/01 07:28:21

  Modified:    doc/reference/en/modules  security.xml
  Log:
  fixed typo, minor changes
  
  Revision  Changes    Path
  1.16      +19 -19    jboss-seam/doc/reference/en/modules/security.xml
  
  (In the diff below, changes in quantity of whitespace are not shown.)
  
  Index: security.xml
  ===================================================================
  RCS file: /cvsroot/jboss/jboss-seam/doc/reference/en/modules/security.xml,v
  retrieving revision 1.15
  retrieving revision 1.16
  diff -u -b -r1.15 -r1.16
  --- security.xml	31 Jan 2007 10:36:44 -0000	1.15
  +++ security.xml	1 Feb 2007 12:28:21 -0000	1.16
  @@ -210,7 +210,7 @@
             annotation.  If both a method and it's declaring class are annotated with <literal>@Restrict</literal>,
             the method restriction will take precendence (and the class restriction will not apply).  If a method
             invocation fails a security check, then an exception will be thrown as per the contract for
  -          <literal>Identity.checkRestriction()</literal>.
  +          <literal>Identity.checkRestriction()</literal> (see Inline Restrictions).
           </para>
           
           <para>
  @@ -262,11 +262,11 @@
             Before we go any further, let's address the <literal>#{s:hasRole()}</literal> expression seen in the above
             example.  Both <literal>s:hasRole</literal> and <literal>s:hasPermission</literal> are EL functions, which
             delegate to the correspondingly named methods of the <literal>Identity</literal> class. These
  -          functions can be used within any EL expression throughout the entirity of the security API.
  +          functions can be used within any EL expression throughout the entirety of the security API.
           </para>
   
           <para>
  -          Being an EL expression, the value of the <literal>@Restrict</literal> annotation may reference objects that
  +          Being an EL expression, the value of the <literal>@Restrict</literal> annotation may reference any objects that
             exist within a Seam context.  This is extremely useful when performing permission checks for a specific
             object instance.  Look at this example:
           </para>
  @@ -328,7 +328,7 @@
       </sect2>
       
       <sect2>
  -      <title>Securing the user interface</title>
  +      <title>Security in the user interface</title>
         
         <para>
           One indication of a well designed user interface is that the user is not presented with options for