Thanks for the tip on the on the issue number. I confess, I don't really understand the super-source solution, or even how it actually solves the problem.
I've resigned myself to know that I'll never be able to build a data-object for the client and then subclass that for the server side because most of our server side objects already inherit from other classes and often have logging components, authentication checks, etc. that would make it pretty complicated. Maybe the server-only option is too complicated to implement sanely, but it sure seemed alluring that the client code would be written in Java and we'd get some real cross-benefits, but I think it's more myth than reality regarding how these can be shared/reused, which is a shame when you consider the various data validations (required/or not, min/max lengths/values, legal characters, etc.) even for simple data objects end up being duplicated, one for the client side and the other for the server side. The one upside of JSP/servlet is that there was no client-side, but now we're moving back to the days of needing two distinct apps, one written for the client, and the other written for the server. I really like GWT, but wish more of these could somehow have been handled more auto-magically <smile>. -- 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.
