[jboss-cvs] jboss-seam/doc/reference/en/modules ...
Shane Bryzak
Shane_Bryzak at symantec.com
Tue Feb 13 05:40:30 EST 2007
User: sbryzak2
Date: 07/02/13 05:40:30
Modified: doc/reference/en/modules security.xml
Log:
JBSEAM-799
Revision Changes Path
1.31 +5 -3 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.30
retrieving revision 1.31
diff -u -b -r1.30 -r1.31
--- security.xml 12 Feb 2007 07:55:49 -0000 1.30
+++ security.xml 13 Feb 2007 10:40:30 -0000 1.31
@@ -330,7 +330,7 @@
<programlisting>
<![CDATA[
- <security:identity authenticate-method="#{authenticator.authenticate}" jaasConfigName="other"/>
+ <security:identity authenticate-method="#{authenticator.authenticate}" jaas-config-name="other"/>
]]>
</programlisting>
</sect3>
@@ -378,9 +378,11 @@
<para>
Seam components may be secured either at the method or the class level, using the <literal>@Restrict</literal>
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
+ the method restriction will take precedence (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> (see Inline Restrictions).
+ <literal>Identity.checkRestriction()</literal> (see Inline Restrictions). A <literal>@Restrict</literal>
+ on just the component class itself is equivalent to adding <literal>@Restrict</literal> to each of its
+ methods.
</para>
<para>
More information about the jboss-cvs-commits
mailing list