I am currently performing a response.sendRedirect (..) which appears
to do the job but fear this may not be the best way to achieve what I
am looking for.
Any help is appreciated. Thanks.
The other option is to use a request dispatcher. This is basically a
servlet calling another servlet, but it sounds like your gwt is using
plain-old html, and not a jsp, so I think the dispatcher would be over
kill.
So, in summary, I think you're doing it right! :)
Also, the difficulty I am encountering with the sendRedirect or
request dispatcher approach is that once a user has signed out of the
application, I have a "login again" link which invokes the same
AuthenticatorServlet which redirects to the GWT initial html page and
this redirect fails with a message that the "response has already been
committed". I am essentially looking for some technique to avoid this
message upon second login from the user.
Thanks.
> > Any help is appreciated. Thanks.- Hide quoted text -
>
> - Show quoted text -
Sure, your gwt doesn't care what it is embedded in, html, jsp, asp, php, etc.
> Also, the difficulty I am encountering with the sendRedirect or
> request dispatcher approach is that once a user has signed out of the
> application, I have a "login again" link which invokes the same
> AuthenticatorServlet which redirects to the GWT initial html page and
> this redirect fails with a message that the "response has already been
> committed". I am essentially looking for some technique to avoid this
> message upon second login from the user.
This error usually means you've written to the output stream before
you send the redirect. I'm fairly certain if you avoid that you won't
get this error.
Good luck!