[
https://issues.apache.org/jira/browse/DELTASPIKE-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13501784#comment-13501784
]
Shane Bryzak commented on DELTASPIKE-292:
-----------------------------------------
My apologies, you are correct that it wouldn't be ambiguous (I did't notice
that the methods had different parameter types).
> @SecurityBindings don't respect parameter types of @SecureParameterBinding
> parameters when determining the authorization method
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: DELTASPIKE-292
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-292
> Project: DeltaSpike
> Issue Type: Improvement
> Components: Security-Module
> Affects Versions: 0.3-incubating
> Reporter: Arne Limburg
> Assignee: Arne Limburg
>
> The following beans lead to the following exception:
> org.apache.deltaspike.security.api.authorization.SecurityDefinitionException:
> Ambiguous authorizers found for security binding type
> @ApplicationScoped
> public class SecuredBean
> {
> @CustomSecurityBinding
> public boolean getBlockedResult(@MockParamBinding MockObject mockObject)
> {
> return mockObject.isValue();
> }
> public boolean getResult(MockObject mockObject)
> {
> return mockObject.isValue();
> }
> }
> @ApplicationScoped
> public class CustomAuthorizer
> {
> @Secures
> @CustomSecurityBinding
> public boolean doSecuredCheck(@MockParamBinding MockObject obj,
> InvocationContext invocationContext)
> throws Exception
> {
> return obj.isValue();
> }
>
> @Secures
> @CustomSecurityBinding
> public boolean doSecuredCheck(@MockParamBinding MockObject2 obj)
> {
> return obj.isValue();
> }
> }
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
