authorized button enablement

Ian Springer ian.springer at redhat.com
Fri Apr 8 16:56:51 UTC 2011


s/MANAGE_SETTINGS resource perm/MANAGE_SETTINGS global perm/

On 04/08/2011 12:35 PM, Ian Springer wrote:
> My changes were in AbstractAlertDefinitionsView, which is the base class
> for resource, group, and template alertdef list views. Because the table
> actions are created in this base class, it would be hard to use the
> authorized table action classes, since the resource and group views
> would have to use ResourceAuthorizedTableAction (for MANAGE_ALERTS
> resource perm), but the template view would have to use
> AuthorizedTableAction (for MANAGE_SETTINGS resource perm). So I'm going
> to leave this one as if for now, since I think it will keep the code
> more succinct. If there was a single AuthorizedTableAction that
> supported both resource and group perms, then using it in this case
> would make more sense.
>
> On 04/07/2011 09:15 AM, Jay Shaughnessy wrote:
>> I saw a check-in yesterday that I think added some global authorized
>> button enablement. I wanted to call attention to AuthorizedTableAction
>> and ResourceAuthorizedTableAction, which may help out when dealing
>> with button enablement and permission checks.
>>
>> Jay
>


-- 
Ian Springer
Principal Software Developer
JBoss Operations Network
Red Hat
ian.springer at redhat.com



More information about the rhq-devel mailing list