An Exception is expected from RPC if it is declared (in which case the compiler will have generated the required Serialization code).
I find declaring your RuntimeExceptions to be "good practice" anyways, since it notifies developers that can't see your source code of what Exceptions may be thrown (even if they don't catch and handle them). It also serves to inform IDE's of what catch statements to generate. There is no need for a patch to the RPC class (someone can correct me if I'm wrong, but it may even be dangerous, since I'm not sure the compiler will see a need for the Serialization code to be generated). Hope that helps, Jason. deanhiller wrote: > Can someone add the following code to RPC.isExpectedException(Method > serviceIntfMethod, Throwable cause) at the very beginning...... > > if(cause instanceof RuntimeException && cause instanceof > IsSerializable) > return true; > > Can someone fix this? I can't throw a RuntimeException as this code > prevents it!!!! It turns it into a StatusCodeException with > exc.getCause returning null. My Exception implements IsSerializable > so I think it should be allowable but GWT code does not allow it :(. > This is a quick bug fix. Where can I post it to get it into the next > release? > > thanks, > Dean > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
