Hi everyone,
what is a reasonable setup/realization for enabling restoring RPCs
after a session timeout, server restart/disconnect and re-login?
Take the following scenario:
- GWT application on standard Tomcat
- container managed authentication via login.jsp (simply redirects to
GWT html upon
Can you give me an example on how I'd be able to resubmit an RPC with
Ray's command pattern approach?
On Feb 6, 5:50 am, Thomas Broyer t.bro...@gmail.com wrote:
On Feb 5, 10:24 pm, Jamie jsgreenb...@gmail.com wrote:
Hi everybody. I'm trying to extend AsyncCallback to always have the
On 8 fév, 18:15, Jamie jsgreenb...@gmail.com wrote:
Can you give me an example on how I'd be able to resubmit an RPC with
Ray's command pattern approach?
I cannot give you a working example, but you'd likely queue all issued
commands and only dequeue them onSuccess. When you think you have to
On Feb 5, 10:24 pm, Jamie jsgreenb...@gmail.com wrote:
Hi everybody. I'm trying to extend AsyncCallback to always have the
same behavior onFailure. I can successfully catch the session timeout
exception that I'm looking for, open a login dialog, and have the user
login. What I want to do
Hi everybody. I'm trying to extend AsyncCallback to always have the
same behavior onFailure. I can successfully catch the session timeout
exception that I'm looking for, open a login dialog, and have the user
login. What I want to do after that is done is to resubmit the
original RPC call that
This is one area where gwt could improve.
We ended up patching ProxyCreator (look up the class) to automatically
retry any requests with strange error codes (0, 12090, 400), and now
that I think about it, it would be nice to do this for session
timeouts as well.
It would be great if gwt could
