From what I have read, not tried yet but planning on soon: You can
take JDO object, make it serializable, and mark it transient, then
you can send it to the client. The client can then use it and send it
back. But you cant just add it back as a JDO object because it is now
a new object. You
Do you have any sample code of login app?
thanks
On Thu, Dec 31, 2009 at 5:34 AM, marcelomos marcelo.mosc...@gmail.comwrote:
hola he usado HIbernate + jPA con mysql y si tengo problemas de
serializacion con la version 2.0 gwt veo que persiste el problema asi
que sigo trabajando con la
Skip JDO/JPA and use something like
http://code.google.com/p/objectify-appengine/ which uses *real* POJOs
for your domain objects. They will transfer through GWT-RPC just
fine.
Jeff
On Fri, Dec 25, 2009 at 11:10 AM, GWTCurious sad...@gmail.com wrote:
I have seen some messages mentioning that
I guess I posted this question on the wrong day. :-) Has anybody the
answer?
--
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-tool...@googlegroups.com.
To unsubscribe from this group, send
hola he usado HIbernate + jPA con mysql y si tengo problemas de
serializacion con la version 2.0 gwt veo que persiste el problema asi
que sigo trabajando con la version 1.7 gwt, las librerias GILEAD
soportan solo la version 1.7 gwt.
estoy esperando la proxima version para la solucion de
I have seen some messages mentioning that with gwt 2.0 it is possible
now to transfer jdo domain objects on app engine / data nucleus to the
client side using standard gwt-rpc mechanism. But I could not find any
information regarding this in GWT documentation. So I would like to
know whether this
