Thanks man! Saved me a few hours for sure. Can't believe nobody needed this yet - should be a part of GWT.
It's not that I want to send a Text or a Blob via RPC - but I definitelly want my data classes to be usable at the client side (translatable). The Text I'm going to put in a String in a JDO load callback function, so that it can be RPC'ed to client and used in a standard string-ish way, and similarly in the other direction. The separation of the jars into client and server was a bit confusing to me, however I've added both into my project's classpath and then included the gwt.xml, and it seems to work. Btw. the gwt.xml (same contente) is in both of these jars - is that a bug or am I doing something wrong? thanks again, J. On Jun 12, 7:48 am, bcottam <[email protected]> wrote: > okay, so I dug into this a bit and figured out how to port existing > code to GWT compliant standards. I also included > _CustomFieldSerializers. I am currently only using Key andTextin my > test code, but I ported Key,Text, Blob, ShortBlob, Link and User > however I haven't tested much beyond the Key andTextclasses. > > here is a link to the jars and some notes about > them:www.resmarksystems.com/code > > I hope it is helpful :) > -bryce > > On May 14, 11:22 am, bcottam <[email protected]> wrote: > > > yeah, I actually posted there > > first:http://groups.google.com/group/google-appengine-java/browse_thread/th... > > and they suggested that I cross-post here :) > > > I actually started using the persisteddataclasses and sending them > > across the gwt rpc channel, and that was fine until the datanucleus > > JDO started putting fields on my classes that were instances of Object > > [] (which don't serialize all that well). That, and I know there is > > going to be a performance hit with sending a lot ofdataover the > > channel. So, I am thinking that doing a lite DTO just for transport > > would possibly be my best option. > > > I will check out Ray Cromwells posts, mainly I guess what I am looking > > for at this point is a good reference for using the "super-source" tag > > and how to make custom wrappers for non GWT classes (in the same > > manner that the java.util api is wrapped with com.google.emul etc. > > Any pointers in that direction would be great. > > > thanks! > > > On May 13, 7:59 pm, Alyxandor <[email protected]> > > wrote: > > > > I'm really not sure, but I'd recommend checking out theAppengine > > > google group > > > first...http://groups.google.com/group/google-appengine-java?hl=en > > > > There's over a hundred posts a day there, so I'm sure someone there > > > with a little more expertise than yours truly will be of more help. > > > > Out of curiosity, have you already tried sending your persistentdata > > > classes down the wire? Cos.... There's a lot of discussion about it, > > > and some workarounds {basically, the only ways I could do it was with > > > Ray Cromwell's various hacks, or a drop-in called Gilead}. You might > > > find that using the same beans to be nigh impossible without making > > > them non-detachable {read: you can send an object to the client, > > > modify it and send it back to the server to save without copying the > > > object, or manually copying thedatafrom every field}. > > > > ...Check the other group, like I said... I'm no expert. > > > > Of course, Ray Cromwell IS, so if you can find his Google-Groups > > > profile, try clicking on some of the threads he posts on... You'll be > > > glad you did! > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
