Totally valid concern. A lot depends on your situation and the purpose of your app. One alternative is the RequestFactory. I've not used it myself, however.
Another alternative is to just detach your domain objects and send them to the client. You'll want to be sure there's nothing in there you don't want your client to see, of course. And then you might have some conflicting needs between making your model good for business purposes vs. making them convenient for your UI. Personally, I'm not a big fan of DTOs, but, in GWT-land, I think they make a lot of sense. I don't have a 1-to-1 mapping of domain object to DTOs, but rather try to design my DTOs for a particular UI need. It's still more work, but (I think) my UIs end up being better, stronger, faster ... whoops, got carried way. :) But YMMV. -- 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/-/MAG3sVnEncoJ. 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.
