This combined with the post just after sounds like the best solution so far(though educating developers on using the adapter is a pain, it will have to do).
In that case though, if I am using tomcat with straight GWT, can I still do this? I don't know much about spring at all. Can I get more details on how to specify the servlet in this case as don't you need to specify the Spring servlet or specify the layer in between GWT Servlet and client somehow. What does the code look like and what does the web.xml look like here? On Oct 2, 1:25 am, 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 Google-Web-Toolkit@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
