[
https://issues.apache.org/jira/browse/WICKET-5143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Grigorov resolved WICKET-5143.
-------------------------------------
Resolution: Fixed
Fix Version/s: 6.8.0
Assignee: Martin Grigorov
I've removed 'final' for the class.
Please create a new ticket with an attachment in .patch format if you prefer
the interface based solution for Wicket 7+.
> 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
> Assignee: Martin Grigorov
> Priority: Minor
> Fix For: 6.8.0
>
> 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
