Maybe. But I gave up, after turned out, that I can't persist the
object even if I manage to pass it to the server. I got various
errors, while I was trying to make it work with JPA or JDO. Now I've
found Objectify which sounds promising. Well I'll see. As for now, I'm
delaying the client-server co
>
> actually I was using simple gwt-rpc to send the object to the server.
>
May be your @Embeddable was enhanced by the JPA provider in a way that made
it incompatible with GWT-RPC?
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To p
actually I was using simple gwt-rpc to send the object to the server.
But I'll check this out. Thanks.
On Jan 13, 2:33 am, Y2i wrote:
> Are you using ValueProxy for @Embeddable?
>
> Take a look at this
> post:https://groups.google.com/forum/#!topic/google-web-toolkit/GtYo9DJaf9...
--
You recei
Are you using ValueProxy for @Embeddable?
Take a look at this post:
https://groups.google.com/forum/#!topic/google-web-toolkit/GtYo9DJaf9o/discussion
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to goo
Hi,
In my app, I wanted to use JPA for persisting into the database.
The object I want to persist is pretty complex, and contains other
classes.
I tried to pass the object from the client to the server,
but it seems I can't send classes with @Embeddable annotation.
"An IncompatibleRemoteServiceE
