It looks like the onFailure case only unfreezes the context in the case of onTransportFailure or response.getGeneralFailure, not in the case of an invocation failure. I tested this, and the context is still locked and the beans still frozen when my onFailure callback is called.
I guess I'll look a bit deeper and see if I can find a way to get my errors returned through the OnViolation callback. Thanks, Eric -- 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/-/8m7ZTvjLbCsJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
