The answers are here: http://code.google.com/intl/hu-HU/webtoolkit/doc/latest/DevGuideServerCommunication.html#DevGuideSerializableTypesand here: http://gwt-code-reviews.appspot.com/47807 and here: http://timepedia.blogspot.com/2009/04/google-appengine-and-gwt-now-marriage.html
In short: JDO enhanced classes with detachable=true can not be received correctly by GWT without additional ugly workarounds, even if the Restlet GWT Converter provides the "correct" representation. On Wed, Aug 24, 2011 at 07:06, Joscha Feth <[email protected]> wrote: > Even if I factor out an interface without the annotations and return this > in the according ServerResource, it seems as if the GWT serializer still > serializes protected fields on the implementation. Has anyone else seen > this? > > Cheers, > Joscha > > > On Wed, Aug 24, 2011 at 04:47, Joscha Feth <[email protected]> wrote: > >> Hello list, >> >> is there any way to ignore a specific field (like the @*JsonIgnore >> *annotation >> in Jackson) of an entity or use a different serializer with additional >> options when using GWT serialization? >> When detaching an object from JDO there is an jdoDetachedState added which >> contains an Object of type javax.jdo.identity.StringIdentity and this can >> not be deserialized on the client side... >> >> Kind regards, >> Joscha Feth >> > > ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2829300
