Jaun,
Our application is nearly 100% custom components. We did not use many of
the default GWT widgets. We also used UiBinder for everything and thus most
screens are a bundle of widgets stitched together with UiBinder.
If there was a custom panel/button/widget, it would have a
setUserEntitlement() method. Then in the .ui.xml you can have
<someNameSpace: myCustomWidget userEntitlement = {ADD_ITEM} />
Now those components will check for their entitlement on load from a
globally available *UserEntitlements[] *that was loaded at application
startup and enable themselves if authorized. A nice thing about this is all
the entitlements are just enums in the UiBinder so you get compile time
checking of that too, and no entitlements hardcoded in Java files.
Of course users can hack the UI, so there is also a backend method level
check for RPC's.
Sincerely,
Joseph
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-web-toolkit/-/Q3sj4dgUmzkJ.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
