I think the field is static to allow multiple instances of the same servlet (for the same servlet-mapping, which I believe is allowed by the servlet spec) share the state, which is static anyway (what's cached is only what's derived from classes and interfaces).
If your ServiceLayerDecorator intercepts createDomainObject, loadDomainObject(s), getProperty, setProperty and invoke, it should work. I'd rather have a single servlet-mapping that works whether the user is authenticated or not, and filters some calls out for unauthenticated requests (and/or checking the authenticated user's authorizations) -- 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/-/dzA2RVdsaWJVdkVK. 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.
