You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "Kamil (JIRA)" <ji...@apache.org> on 2017/09/04 16:26:00 UTC

[jira] [Commented] (WICKET-6463) Please add additional constructor to Roles

    [ https://issues.apache.org/jira/browse/WICKET-6463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16152781#comment-16152781 ] 

Kamil commented on WICKET-6463:
-------------------------------

By the way, AnnotationsRoleAuthorizationStrategy#L174 checks "isEmpty(acceptedRoles) || hasAny(acceptedRoles)" while hasAny(Roles) does exactly the same check

> Please add additional constructor to Roles
> ------------------------------------------
>
>                 Key: WICKET-6463
>                 URL: https://issues.apache.org/jira/browse/WICKET-6463
>             Project: Wicket
>          Issue Type: Improvement
>            Reporter: Kamil
>            Priority: Trivial
>
> org.apache.wicket.authroles.authorization.strategies.role.Roles can be initialized using String[], but it should be also possible to initialize it using any Collection<String> (since it's already a HashSet, it should be pretty strightforward)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)