It's easy with Locator to apply permissions on "data retrieval". With 
ServiceLocator, you can just as easily wrap your service instance behind a 
proxy responsible for checking permissions on methods (or, if you use Guice 
or Spring, you'll get the instance from there and have them apply AOP 
interceptors). You can also use a ServiceLayerDecorator to do all the above, 
and/or implement some kind of AOP on your services (that's what we're doing, 
it works very well: override invoke() to check permissions, based on 
annotations on the called method)

-- 
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/-/VzZ1bjJRLVJoa2tK.
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.

Reply via email to