Thursday, December 29, 2011

Re: RequestFactory - Intermittent "The AutoBean has been frozen" on newly created

In your addOrUpdate() method, check to see you are returning the exact same instance that was passed in, just remembered I did actually run into the same problem when you return a different instance that has the same identity. 


On Thu, Dec 29, 2011 at 4:38 PM, Jeff Rodriguez <jeff@jeffrodriguez.com> wrote:
Yeah, I put that code into a click handler for a button so I can just
repeatedly fire it off. It's the only code in the function.

It seems like something is trying to edit the result before my
receiver callbacks are called. I say that because it works on the
server side every single time. If I click that button 5 times, I'll
end up with 5 entities in my data store.

On Dec 28, 10:09 am, "Aidan O'Kelly" <aida...@gmail.com> wrote:
> From the code you posted, it should work fine (even the original code). Is
> it all executed in one function? It sounds like there's some paths of
> execution which differ from it, and somehow end up calling setName() on a
> frozen proxy.

--
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.


--
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.

No comments:

Post a Comment