[jboss-cvs] jboss-seam/doc/reference/en/modules ...
Gavin King
gavin.king at jboss.com
Tue Jan 30 11:32:37 EST 2007
User: gavin
Date: 07/01/30 11:32:37
Modified: doc/reference/en/modules security.xml
Log:
permission should be named render
Revision Changes Path
1.12 +2 -2 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.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- security.xml 30 Jan 2007 13:14:10 -0000 1.11
+++ security.xml 30 Jan 2007 16:32:36 -0000 1.12
@@ -407,7 +407,7 @@
Page security requires that the application is using a <literal>pages.xml</literal> file, however is
extremely simple to configure. Simply include a <literal><restrict/></literal> element within
the <literal>page</literal> elements that you wish to secure. By default, if a value is not provided for the
- <literal>restrict</literal> element, an implied permission of <literal>{viewId}:view</literal> will
+ <literal>restrict</literal> element, an implied permission of <literal>{viewId}:render</literal> will
be checked for whenever accessing that page. Otherwise the value will be evaluated as a standard
security expression. Here's a couple of examples:
</para>
@@ -426,7 +426,7 @@
<para>
In the above example, the first page has an implied permission restriction of
- <literal>/settings.xhtml:view</literal>, while the second one checks that the user
+ <literal>/settings.xhtml:render</literal>, while the second one checks that the user
is a member of the <literal>admin</literal> role.
</para>
More information about the jboss-cvs-commits
mailing list