Jeff,
Thanks for the quick response. Yes, basically if you follow the
normal application flow you loose the gwt.codesvr parameter and
therefore the debug module logic doesn't work.
As for the authentication, we do authenticate people outside of GWT.
Our login process is actually done via
Hi Adam:
I get what you're saying.
Do you have control over the logout hook? If so, why not add some
intelligence that copies the gwt.codesvr parameter if it exists in the URL?
I don't see any security implications here (perhaps I'm not sufficiently
caffeinated)
On Wed, May 26, 2010 at 5:25 AM,
Jeff,
Yeah I have a working prototype of that working now. The route we've
decided to take though is to have a developer mode and if set a
request filter will auto authenticate allowing direct connection to
GWT EntryPoint URLS with gwt.codeSvr included.
Thanks for all your help Jeff.
-Adam
On
You should join us in voting for
http://code.google.com/p/google-web-toolkit/issues/detail?id=4367
On May 26, 9:24 am, Adam ambr...@gmail.com wrote:
Jeff,
Yeah I have a working prototype of that working now. The route we've
decided to take though is to have a developer mode and if set a
Hey Gang,
I'm having an issue with DevMode working properly. We're using
noserver option and instead connecting to our JBoss application. I've
configured the GWT Plugin in Eclipse to point to our entrypoint page.
The issue is that container security redirects us to authenticate to
the
On 05/25/2010 01:14 PM, Adam wrote:
Hey Gang,
I'm having an issue with DevMode working properly. We're using
noserver option and instead connecting to our JBoss application. I've
configured the GWT Plugin in Eclipse to point to our entrypoint page.
The issue is that container security
