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

Posted to commits@wicket.apache.org by "Nuno Jacinto (JIRA)" <ji...@apache.org> on 2013/04/13 11:52:15 UTC

[jira] [Created] (WICKET-5143) Create an interface for the roles replacing the current Roles class

Nuno Jacinto created WICKET-5143:
------------------------------------

             Summary: Create an interface for the roles replacing the current Roles class
                 Key: WICKET-5143
                 URL: https://issues.apache.org/jira/browse/WICKET-5143
             Project: Wicket
          Issue Type: Improvement
          Components: wicket-auth-roles
    Affects Versions: 6.6.0
            Reporter: Nuno Jacinto
            Priority: Minor


Currently the roles in wicket are managed by a final class, Roles, that extends HashSet.
In my current projects I have to manage permissions considering several factors that include the role, the creator and the type of data, and this must be done also when displaying tables with several rows. Having the possibility to create my own Roles class I can integrate my restrictions with wicket authorization and add some performance improvements (required in this case because the validation must be done at the field level). 

--
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