Hi Dean, I'm not familiar with the concept of SDO but if I understand your point, you would like to create a generic object model on the UI side and the build reusable widgets on top.
In fact, I already got a solution working based on a simplified JSON- RP: http://ffxml.net/gwt-json-rpc.html You wrote: "the near-ultimate SDO implementation in RPC's is List<Map<String, T>> , according to the Spec http://en.wikipedia.org/wiki/Service_Data_Objects, but it's not language agnostic. Check out JSON http://www.json.com/"; With my current solution, from a JSON message, I obtain a HashMap<String, Object> But it seemed to me that using overlay types would achieve the ultimate efficiency. Internally, a JSON object is just like a HashMap. Generic getters/ setters would be useful to bind the UI to the model. Emanuel On Jun 5, 2:20 pm, "Dean S. Jones" <deansjo...@gmail.com> wrote: > I've been down this path a few times, and it's the reason I have > posted on this group more than once about "Not using domain objects in > the UI"... > > http://groups.google.com/group/Google-Web-Toolkit/browse_thread/threa... > > I can see you are already falling back to get/set fields by name, so > you are about halfway to the point of discovering what I eventually > found out: generic data models will make life much much easier. > Binding them to Widgets and validation is a breeze comparatively. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
