Author: fpapon
Date: Sat Feb 9 14:26:41 2019
New Revision: 1853282
URL: http://svn.apache.org/viewvc?rev=1853282&view=rev
Log:
merging shiro site pr-42
Modified:
shiro/site/publish/java-authorization-guide.html
Modified: shiro/site/publish/java-authorization-guide.html
URL:
http://svn.apache.org/viewvc/shiro/site/publish/java-authorization-guide.html?rev=1853282&r1=1853281&r2=1853282&view=diff
==============================================================================
--- shiro/site/publish/java-authorization-guide.html (original)
+++ shiro/site/publish/java-authorization-guide.html Sat Feb 9 14:26:41 2019
@@ -336,7 +336,7 @@ if(currentUser.isPermitted(perm)){
}
</code></pre>
<p>You can construct the permission string the way you want so long as your <a
href="realm.html" title="Realm">Realm</a> knows how to work with it. In this
example we use Shiro’s optional permission syntax, <a
href="permissions.html" title="Permissions">WildCardPermissions</a>.
WildCardPermissions are powerful and intuitive. If you’d like to learn
more about them then check out the <a
href="static/current/apidocs/org/apache/shiro/authz/Permission.html">Permissions
Documentation</a>.</p>
-<p>With string-based permission checks, you get the same functionality as the
example before. The benefit is that you are not forced to implement a
permission interface and you can construct the permission via a simple string.
The downside is that you don’t have type safety and if you needed more
complicated permission capabilitues that are outside the scope of what this
represents, you’re going to want to implement your own permission objects
based on the permission interface.</p>
+<p>With string-based permission checks, you get the same functionality as the
example before. The benefit is that you are not forced to implement a
permission interface and you can construct the permission via a simple string.
The downside is that you don’t have type safety and if you needed more
complicated permission capabilities that are outside the scope of what this
represents, you’re going to want to implement your own permission objects
based on the permission interface.</p>
<a name="JavaAuthorizationGuide-AnnotationAuthorization"></a>
<h3><a href="#annotation-authorization"
name="annotation-authorization">Annotation Authorization</a></h3>
<p>If you don’t want to do code level authorization checks, then you can
use Java Annotations as well. Shiro offers a number of <a
href="java-annotations-list.html" title="Java Annotations List">Java
annotations</a> that allow you to annotate methods.</p>
