I don't have the *_CustomFieldSerializer in the translatable path either so it wouldn't be able to sent over the wire. But this I've found is only half of the recipe and just checking the signature. So I'm looking at the generator or serialization oracle.
Brandon
On Wednesday, January 2, 2013 7:38:36 AM UTC-8, Colin Alworth wrote:
It looks like it thinks you are sending the CustomFieldSerializer itself over the wire, so wants to find a serializer serializer... The extra prefixed package name "com.google.gwt.user.client.rpc.core" indicates that it wasn't able to find your field serializer in the normal package where it should be - consider knocking off that part and just make a com.googlecode. objectify.impl.ref.StdRef_CustomFieldSerializer with the appropriate static methods.
In my brief re-read, I'm not seeing anywhere where the serializer gets passed in as a class to find another serializer for it - this fits with my previous experience where you just create a serializer and let RPC invoke it, no questions asked.
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/vo66cUkmZZwJ.
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.
No comments:
Post a Comment