From fd1af34add56cbf04facc9feadb3b03ba8ad4bae Mon Sep 17 00:00:00 2001 From: Luke Taylor Date: Tue, 21 Apr 2009 06:06:13 +0000 Subject: [PATCH] Minor javadoc stuff. --- .../springframework/security/acls/vote/AclEntryVoter.java | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/acl/src/main/java/org/springframework/security/acls/vote/AclEntryVoter.java b/acl/src/main/java/org/springframework/security/acls/vote/AclEntryVoter.java index 959787c6b5..f26aa2d4d7 100644 --- a/acl/src/main/java/org/springframework/security/acls/vote/AclEntryVoter.java +++ b/acl/src/main/java/org/springframework/security/acls/vote/AclEntryVoter.java @@ -55,11 +55,12 @@ import org.springframework.util.StringUtils; * method. *

* If the method argument is null, the voter will abstain from voting. If the method argument - * could not be found, an {@link org.springframework.security.access.AuthorizationServiceException} will be thrown. + * could not be found, an {@link AuthorizationServiceException} will be thrown. *

* In practical terms users will typically setup a number of AclEntryVoters. Each will have a - * different {@link #processDomainObjectClass}, {@link #processConfigAttribute} and {@link #requirePermission} - * combination. For example, a small application might employ the following instances of AclEntryVoter: + * different {@link #setProcessDomainObjectClass processDomainObjectClass}, {@link #processConfigAttribute} and + * {@link #requirePermission} combination. For example, a small application might employ the following instances of + * AclEntryVoter: *