I agree with drunningw. I couldn't have said it better myself. For the most part it's a design decision. However in the same way that super servlets are considered to be anti-pattern, a super service class would also be considered an anti-pattern. I'll also add that from a team development standpoint, it may be easier to have smaller service classes. It facilitates team development by making sure that you don't run into situations where multiple developers need to work on the same service class. It also helps avoid version control collision.
Depending on how sophisticated your back-end services are, you may situations where your service methods need to be in different services to support different lifecycle or transactional requirements. When I develop GWT services using Spring, I can control transactional properties and scope at the service level. HTH On Jan 12, 5:19 pm, drunningw <[email protected]> wrote: > However, clarity of intent should be the guiding principle.
-- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. 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.
