I'm running into this issue too. It seems when the server throws an exception it gets sent to the individual Request not the fail() method in the RequestContext. So reuse() is never called from it in the case of a server exception. I'm not sure why they designed it this way. A server exception should do a fail for the overall RequestContext not for an individual request. There are many cases where you would want to be able to resubmit a request after a server exception (in my case it was a column was the wrong type in my database and so JDBC was throwing an exception about it and once the column is changed, I want to be able to resubmit it on the client-side, but I can't due to the fact that the request still says it's locked). Except for subclassing AbstractRequestContext and overriding the processPayload to act the same no matter the failure type, or writing a JSNI to get to reuse() on a context, I'm not sure how to fix this. Does everyone else feel that reuse() should be called no matter what the cause of the exception?
-- 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/-/kjqWzUE9xRMJ. 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.
