In MVC, the model is heavy with business rules and data access, the view contains the presentation logic, and the controller is typically a framework component with an XML configuration to drive it. In MVP, the model is lightweight POJO value objects, the view is mockable, and the presentation is specific to the model and the view. It is the presentation that has all the dependencies and glue code for the model and the view. You get more code coverage in your unit testing with MVP so MVP and TDD go together.
I also talk about MVP in this presentation. http://www.dynamicalsoftware.com/gwt On Mar 28, 10:40 pm, sridevi macherla <[email protected]> wrote: > Hi, > > Can someone brief out about Model View Presenter architecture... > > Thanks > > Sri -- 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.
