On Sep 16, 5:22 pm, Sripathi Krishnan <[email protected]> wrote: > Its up to you to implement it, but I would advise you not to do so. > > Assume you have a DTO which includes two functions - void serverSideOnly() > and void clientSideFunction(). > > You would now have to guarantee that clientSideFunction() doesn't somehow > call serverSideOnly() -- because that would not work in javascript. > > And supposing you end up guaranteeing the above, it means you have two sets > of functions in your class which don't speak to each other. Which means they > have no business being together in the same class. You could just make a > ServerSideDTO that extends from your ClientSideDTO and add the extra > methods.
I understand the issues and I've built prototypes on various workarounds. The other stuff I do on my system depends on the DTOs being the way they are. They are, in fact, auto-generated for use with another framework. Refactoring them to make sense in this case is more expensive for me than tweaking GWT is. I realize that "GWT people" don't want this, precisely for the reasons you cited. It's poor design and breaks assumptions that they currently feel comfortable holding. From my viewpoint, GWT is a minor UI in my bigger system and if something's got to give, it's GWT design integrity. I'm a user. I know what I want. I understand that GWT people may not want me to do it. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
