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

["Nuno Jacinto (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WICKET-5143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nuno Jacinto updated WICKET-5143:
---------------------------------

    Attachment: roles_changes.zip

The attached file contains the changes required. Hopefully I cover all the files. I named the interface IRoles (I think it follows your strategy on names) but please give whatever name you see fit. I extend the interface with IClustered, as it was on the class Roles, and added the interface Collection<String>. Maybe it was necessary to add all methods of Collection but this way I hope to minimize any possible changes on existing projects. Please let me know if it requires more changes or if you make changes so that I can update my local code. Thank you.
                
> 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
>         Attachments: roles_changes.zip
>
>
> 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