All things 'static' are generally seen as "not elegant" in Java, so using a ServiceLocator would make "more elegant". YMMV.
Also, "elegant" doesn't necessarily match with "pragmatic", so there might be additional costs to making things "elegant". If you ask me, I'd go with instance methods and a ServiceLocator (and dependency injection), because it makes testing the service with mock dependencies easier (less error prone, make it possible to test in parallel with different dependency mocks, etc.) -- 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/-/dPztG5JCrSkJ. 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.
