On Mar 7, 5:32 pm, JP seri...@gmail.com wrote:
Fifth, ties with the fourth and is the obvious implementation of
IsSerializable for RPC. Like so:
public class GameData implements IsSerializable {
You shouldn't need to use IsSerializable. Plain old
java.io.Serializable will work fine and keep
Yes it would work, but it doesn't quite communicate the same thing and
doesn't have to mean the same thing either. Both work, but I choose
IsSerializable because I thought Google's reasons were sound and my
code is already bound to GAE and GWT in so many ways that this simple
data-holder structure
I've googled and tried for hours, but I can't find anything to back up
the fact that you can have a JDO enhanced class and pass it through
RPC other than this line in the GWT docs:
... previous versions of GWT were unable to perform RPC on enhanced
classes. As of GWT version 2.0, some common forms
private Key key;
is what is killing your serialization policy as I believe Key isn't GWT
serializable out of the box. Gilead will probably get you what you're
looking for, or else you can use requestfactory/autobeans to manage DTOs.
--
You received this message because you are subscribed
Solved it myself. I'll write it here for reference. I'll assume
you've successfully written a Datastored object in JDO and sent some other
object through RPC before.
First, make sure to follow the weakest links. In my case, RPC/GWT couldn't
handle the URL-class objects and JDO/GAE couldn't
Thanks, you are correct. They Key was killing me, but once I fixed that I
found new problems. I've detailed what I did below.
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To post to this group, send email to
