I want to implement common error handling in all of my RPC onFailure methods. Excluding repeating the error handling code in every invocation I can either 1) extend AsyncCallback and use it in all my invocations or I can 2) extend ServiceInterfaceProxyGenerator and have it generate an implementation of AsyncCallback for me that would include my common error handling. As I already have a lot of RPC calls using the normal AsyncCallback so using option 1 would obviously require refactoring a lot of code. In contrast, were I to use option 2 there would be no refactoring required.
Perhaps the solution seems obvious, which is to use option 2, but I am hoping that you can provide feedback on both of these options and perhaps illuminate any potential problems with either before I commit to one or the other. Thanks a lot for your feedback. -- *Jeff Schwartz* -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. 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.
