We'll definitely update the sample project and doc, thanks for the good
find.
The workaround will in fact work, but I might add a check for the existence
of the gwt.codesvr query param and, if present, add it's value to the
redirect URL.
For example:
String gwtCodeSvrParam = Location.getParameter("gwt.codesvr");
if (!"".equals(gwtCodeSvrParam)) {
signInLink.setHref(loginInfo.getLoginUrl() + "?gwt.codesvr=" +
gwtCdeSvrParam);
}
On Fri, Dec 11, 2009 at 1:50 PM, ziggystardust <[email protected]> wrote:
> Luis' suggestion offered a clue to what is going on here and I have
> managed to figure out what the problem is. The StockWatcher
> application is expanded in the example to include a Google Accounts
> login (i.e. LoginService). What this does is that when the module is
> loaded it checks to see if the users has already logged in. If not it
> refers them to the Google Accounts login and in development mode this
> is simulated. When you pass the page for the URL which the accounts
> login page should return to and it doesn't include the gwt_codesvr=...
> reference you loose the ability to debug the application and make
> changes on the fly after login. This is why I would have to constantly
> recompile the app. When it returned from the login page without the
> gwt_codesvr reference it was picking up the app form the war directory
> which would have been stale.
>
> I suspect Google needs to update the documentation for the
> StockWatcher example. What I had to do is append
> "gwt.codesvr=localhost:9997" to the login and logout URLs. See below
>
> private void loadLogin() {
> // Assemble login panel.
> signInLink.setHref(loginInfo.getLoginUrl() +
> "?gwt.codesvr=localhost:
> 9997");
> loginPanel.add(loginLabel);
> loginPanel.add(signInLink);
> RootPanel.get().add(loginPanel);
> }
>
>
> and
>
>
> signOutLink.setHref(loginInfo.getLogoutUrl() + "?
> gwt.codesvr=localhost:9997");
>
> One needs to be careful hard coding these values though as they may
> change if the browser is running on a machine tht is different than
> where the development server is running or if using a different port
> number.
>
> Not sure if this is the best way to address this and if others have a
> better suggestion I would appreciate it. I would consider this a
> workaround at this point. Thanks Luis.
>
>
> On Dec 11, 9:19 am, Luis Fernando Planella Gonzalez
> <[email protected]> wrote:
> > Make sure you have ?gwt.codesvr=127.0.1.1:9997 at the end of the URL
> > in the browser.
> > That's what makes it use development mode.
> > Otherwise, it will just be the plain old web mode (now called
> > production mode).
> >
> > On 11 dez, 10:46, ziggystardust <[email protected]> wrote:
> >
> >
> >
> > > Been using GWT / App Engine and the Eclipse plugin for some time now
> > > and just recently upgraded to 2.0. I reinstalled Eclipse (3.5),
> > > installed the plugin and the sdks. Setup the example StockWatcher app
> > > and everything runs fine. In dev mode however I have torecompile
> > > whenever i make a change in order for it to be effective. Tried reload
> > > and restarting the browser (IE and Chrome), tried restarting the
> > > server but no joy. Any ideas appreciated. Thanks.
>
> --
>
> 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]<google-web-toolkit%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>
>
>
--
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.
