Re: gwt 2.0 jdo / jpa enhanced classes in App engine / Data Nucleus used for GWT-RPC calls to client side

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 will have to get the JDO object back from the data
store, then update the properties from the new object.

On Dec 25 2009, 1:10 pm, GWTCurious <sad...@gmail.com> wrote:
> 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 works fine for a production application without
> problems? and also if this is limited to JDO and does not support JPA
> or we could also use JPA app engine domain objects with gwt-rpc?
> I have been using GILEAD with JPA+ hibernate + MySQL for this and so
> far encountered no problems. Gilead site mentions that it now supports
> JPA + app engine but it cautions this feature is experimental and
> should not be used for production applications. Does anyone using it?
> Thanks!

--

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-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.