Hi, I am also facing the same issue. In my case, I have also used Acegi Security to implement authorization. If session times out then in this case, Authorization filters of the acegi will not work & control will not be able to reach the GWT Handler. In this case, however, exception would still be thrown. So what alternatives do I have in this case? One that comes to mind is that I can leave authorization rules on the GWT services as these services shall be accessed by someone who has got access to the web page in first case. So no authorization for RPC based services. If there is any authentication error, then the control would reach GWT handler and the aspects can catch them, marshall them and send them back to GWT client.
Comments? Regards, Nitin On Oct 2, 12:25 pm, falafala <[EMAIL PROTECTED]> wrote: > The gwt client cannot interpret the redirect or invalid response > (hence invocation exception). I do it this way... > I use GWT server library so I can implement the service as POJO in > Spring container and published as gwt service. I cannot use servlet > filter bcoz it cannot handle the marshaling of the response. It > should be behind the GWT rpc servlet. So I intercept the call to POJO > service using Spring aop and check the session there, and throw > session expired exception. The "SessionExpiredException" can also > include the URL to be redirected. This can be marshaled and sent back > to the gwt client. > > On the client side, you can catch the SessionExpiredException in the > AsyncCallback handler and call the Javascript to do the redirect. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
