UserMgr is a simple class containing the functionality needed for the UI to do the roles checks, login & logout user etc. The list of roles assigned to the user is not a part of the UserMgr itself but it's a property of the User entity -a simple HashSet to be precise. The UserMgr has a property called currentUser which gives access to the roles. UserMgr offers then a set of role&access check methods for the presenters e.g. public boolean canEdit() etc.
HTH, Lukasz On 7 Mrz., 11:08, csaffi <csaff...@gmail.com> wrote: > Thank you Lukasz. > > > In my app I'm doing the security checks on the client- as well as on > > the server-side. After the user successfully logged into the app, the > > UserManager containes among other things a set of roles which are > > assigned to the current user enabling the role-checks without any rpc- > > callbacks. The client checks are done to provide only the necessary UI > > - only the system functions which can actually be accessed by the > > current user. The server checks provides the "true" security, ensuring > > that only the users with the corresponding rights can access the > > services. > > UserManager is a list of roles assigned to user-groups? So, a key- > value table? -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.