The approach I used in my book was to implement a filter over RPC that translates PersistenSet into Set, date.sql to regular dates, etc. This way I don't need to do squat in my model and all of these issues go away. Just throw whatever you want into the RPC pipe and the GWT incompatible types get transformed in the filter.
The filter is here: http://code.google.com/p/tocollege-net/source/browse/ProGWT/trunk/src/main/java/com/apress/progwt/server/gwt/ServerSerializationStreamWriter2335.java The project is here http://code.google.com/p/tocollege-net/ Unfortunately GWT doens't support this filter concept so I need to keep hacking the ServerSerializationStreamWriter class and I haven't updated past 1.5.RC1 yet. I've moved to rails, so I'm not as active with this project anymore, but if anyone's interested in this approach I think it has a lot of upsides. -Jeff On Nov 6, 11:45 am, "David Durham, Jr." <[EMAIL PROTECTED]> wrote: > On Thu, Nov 6, 2008 at 7:49 AM, Arthur Kalmenson <[EMAIL PROTECTED]> wrote: > > > Hello Dave, > > > We use a common domain object between the client and server side. The > > domain objects are JPA annotated beans, and they travel between the > > client and server. The only think you have to watch out for is > > PersistentSets and other Hibernate specific collections. > > How are you dealing with PersistentSets et al? I see some reference > to a hibernate gwt module and source includes. > > -Dave --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
