>
> I didn't have the time to answer to your comments yesterday.
> *Instead of @RequireRole("superAdmin") you would then use
> @RequirePermission("canMakePersonToAdmin") . *
>
> It's pretty the same: my issue is that I cannot group widgets under the
> same umbrella : nothing says that is a profile "pizzayolo" will have access
> to button A and B in a given solution implementation, the buttons A and B
> will not be able to be accessed by the same profile for a second
> implementation, each will require an independent condition. So I need a per
> widget granularity of permissions.
>
So its a shared/common widget used by other views and depending on which
view uses it the permissions are different? That might be a bit more
complicated in an annotation based solution but should also be possible.
What I was wondering is, if you do that permission thing inside GWT's
FieldWriter then isn't it annoying that you now must assume that all
security relevant @UiFields may be null? So you must do quite a bit of null
checks and deal with the fact that GWT developers normally think that a
@UiField is never null and maybe tend to forget about that?
-- J.
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
