You can intercept it with a ServiceLayerDecorator, but it'd wtill fail, because the RequestFactoryInterfaceValidator will throw when validating the mismatched method. You could add a new method (but not an overload!) in your service though, and then "route" the method call to that method.
But honestly, I'd rather inject a Provider<> (or whatever it's called in Spring DI) into the service and have it retrieve the user ID throught this provider. That's we're doing, except we use Guice for DI, and the user ID is initialized from the ServletRequest#getRemoteUser. -- 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.
