How do you organize your gwt mvc application? - gwt on the view - some java pojos (or ejb3) on the model - ?? on the controller
Considering that you have to show the first name, last name and e-mail address and your User entity has many other fields, do you have a service method "getUserInfo" that return the current user User entity. What do you do? Transfer the entire entity to gwt and format/show just the parts that you need, or you create a DTO to hold just the information that must be shown "first name, last name and e-mail address" ? On Mon, Jun 8, 2009 at 7:03 AM, nellyville<[email protected]> wrote: > > Think about performance too. If you have a bunch of unecessary data > being transferred across the wire your app will be slower. > > On Jun 8, 1:25 am, Keith Whittingham <[email protected]> wrote: >> From an architectural point of view I don't think it's very clean to >> have classes that belong to the server side on the client side. Sooner >> or later I'd regret it I'm sure. No, the more I play around, the more >> I like the model I proposed. The OO model on the client side is likely >> to be different in subtle ways being forced to think about the service >> interface is a good thing on balance. >> >> It would be nice if the *Asych.java file were automatically generated >> though. >> >> On Jun 8, 2009, at 10:03 AM, mnenchev wrote: >> >> >> >> >> >> > What if the persistence layer is ejb for example? >> >> > Miroslav Genov wrote: >> >> You don't have any problems to access client classes from server side >> >> code. Just put all your model classes into client package >> >> and use them in the persistence layer. >> >> >> Kwhit wrote: >> >> >>> I'm building my first serious GWT app and am looking for a >> >>> 'template' >> >>> model to structure things. On the client side I need much the same >> >>> objects to populate the UI as on the server side to handle >> >>> persistence. Let's say I need Employee on the client side to edit >> >>> employee details and then I need Employee on the server side to >> >>> persist it. >> >> >>> As I understand it client side objects must be located in the >> >>> package ....client.* and persistent objects in ...server.*. >> >>> Therefore >> >>> I need two Employee.java files - with slightly different contents - >> >>> the one on the client side acting more or less only as a value >> >>> object. >> >> >>> Have I got things right? > > > > -- Eduardo S. Nunes http://e-nunes.com.br --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
