Only advantage I can see right now is that you can overwrite methods of a super class, e.g. a generic service method which may not fit well for some rare specific sub services.
If you do not need to overwrite methods in services then you are probably fine not using a ServiceLocator. Without a ServiceLocator you still have inheritance of services and you can still put all your service methods into a separate service/DAO class instead of the domain classes. You just cant overwrite methods. -- J -- 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/-/X0O32ehHAz4J. 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.
