I believe that the reason this class existed to begin with was to allow (for some reason..) RPC to serialize that exception and pass it to client code. But emulation that "needs" it to match the correct signature can safely remove it from a "throws" clause without breaking the contract, correct?
Or is this a case of "it isn't a runtime exception, so the _calling_ code must then declare the catch statement"? I'm still waking up, might not be fully clear here... -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/f70256f6-a236-4f8f-b237-a191d44cb112%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
