I've found a way around it: generating custom HTTP response codes on server and handling StatusCodeException on client, but not 100% satisfied with it. Anyone knows a better way to do it?
luisfpg escreveu: > Hi. > Basically any method in my remote servlets may throw some common > exceptions, like PermissionDeniedException, UserDisconnectedException > and so on, but I don't want to declare them in every single method, in > every single service. > Since I use a custom servlet, I tried to hack the serialization policy > to allow those exceptions to be serialized, but if I do so, the client > yields an IncompatibleRemoteServiceException. > Can this be done without having to declare those exceptions in every > method? > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
