Unable to bring up the hosted mode console for my web application

[DanG]

When I create a GWT project in eclipse with gwt2.0.2 and google app
engine 1.3.2 and the most updated eclipse plugin for galileo: I can
create the project but when I run->web application, I get a google
eclipse console ("Development Mode") message telling me the URL I can
access the app from (that's fine), but I get NO gwt hosted mode
console popping up... what am I doing wrong?

More info:

Was using GWT 1.6 before this without the eclipse plugin and
everything was working fine.

I thought maybe I was doing something wrong, but after looking for
info as to how it should work, I'm definitely doing the same as the
following source:
http://www.ibm.com/developerworks/java/library/j-gaej1/

Incidentally I thought it might be the fact that Google App engine
stuff is now there, but if I create a project but I deselect the
"using Google app engine SDK", It still gives me the same problem.

I have other projects created with GWT 1.6 available in eclipse and
they work correctly with the new library.
If I try and create a new -Run Configuration- as a -Java Application-
instead of the new -Web application- and I copy all the settings from
the previous projects, I can run that configuration, I get the hosted
mode, but it gives me the error:

Exception in thread "main" java.lang.NoSuchMethodError:
org.mortbay.thread.Timeout.<init>(Ljava/lang/Object;)V
at org.mortbay.io.nio.SelectorManager
$SelectSet.<init>(SelectorManager.java:306)
at org.mortbay.io.nio.SelectorManager.doStart(SelectorManager.java:
223)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:
39)
at
org.mortbay.jetty.nio.SelectChannelConnector.doStart(SelectChannelConnector.java:
303)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:
39)
at org.mortbay.jetty.Server.doStart(Server.java:233)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:
39)
at
com.google.gwt.dev.shell.jetty.JettyLauncher.start(JettyLauncher.java:
543)
at com.google.gwt.dev.DevMode.doStartUpServer(DevMode.java:421)
at com.google.gwt.dev.DevModeBase.startUp(DevModeBase.java:1035)
at com.google.gwt.dev.DevModeBase.run(DevModeBase.java:783)
at com.google.gwt.dev.DevMode.main(DevMode.java:275)

[Ian Bambury]

Right-click the URL, copy, and paste it into a browser (as it says just above the URL). Then you'll have to install a plug-in.

Ian

http://examples.roughian.com

--
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-we...@googlegroups.com.
To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

[kozura]

Alternatively you can run DevMode as a java application to get the
separate window from Eclipse; I prefer it over the tab. Not sure if
there's some devmode argument you can set to force this window when
running as a Web App. Your error doing this may be due to not putting
the GWT SDK into the classpath properly?

[DanG]

@Ian

So is this the default new behaviour?
The IBM guide I posted says I should get the hosted mode console if I
use the GWT sdk. Is this simply out of date?
Incidentally, if I copy and paste the URL into a browser, the page
fails to load.

I also prefer the hosted mode console for two reasons. I can restart
Jetty in one click which rather than rerunning the configuration.
I got a debug tab in the hosted console for each browser and because
I'm working on a chat like app, this was useful.

On Apr 12, 3:37 am, Ian Bambury <ianbamb...@gmail.com> wrote:
> Right-click the URL, copy, and paste it into a browser (as it says just
> above the URL). Then you'll have to install a plug-in.
>
> Ian
>
> http://examples.roughian.com
>

> > google-web-tool...@googlegroups.com<google-web-toolkit%2Bunsubs cr...@googlegroups.com>

[DanG]

@kozura

I assume the GWT sdk is setup correctly because the field for version
number is populated.

Also, you'll see in my original post that I did try and getting
Devmode running as a java application, but ran into issues.

[kozura]

Right, I was just trying to think back to when I've seen that exact
error you posted, and how I solved it. Jetty is failing to start
because it can't find something it needs, but don't remember what I
did. I do remember debugging it by creating a project using
webAppCreator instead of the with plugin, then importing it to
Eclipse; this creates a Java based application that should work
correctly, bringing up the separate console.

Does anyone know the there's a switch or button that you can turn on
to get the separate console from the web app created by the plugin?

[Christian Schuhegger]

I just wanted to mention that I have the same problem after I updated
the google eclipse plugin to its newest version. I was using gwt 2.0.1
and gae 1.3.1 before. Now I ahve gwt 2.0.3 and gae 1.3.2.

--
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-we...@googlegroups.com.

To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.

[Rajeev Dayal]

Can you list your build path? It seems like there may be some conflicting classes on your build path.

--
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-we...@googlegroups.com.
To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

[Rajeev Dayal]

To clarify, GWT 2.0+ no longer uses the Hosted Browser - it makes use of Out-Of-Process-Hosted-Mode. See code.google.com/webtoolkit/doc/latest/DevGuideCompilingAndDebugging.html for more information.

When using GWT 2.0+ with the Google Plugin for Eclipse, you'll see the "Development Mode View" pop up whenever you launch a GWT 2.0+ application. From this view, you can see the module-based logs, and restart the Jetty server. Server logs are show in the console view.

If you prefer the Swing UI that GWT 2.0+ has (as opposed to the "Development Mode View"), set the following environment variable in your launch configuration:

USE_REMOTE_UI=false

However, we'd be curious to know why you actually prefer the Swing UI to the Development Mode view :).

Thanks,

Rajeev

[kozura]

Ah thanks Rajeev, been looking for that, it works except you have to
set USE_REMOVE_UI=true.

And since you asked... Maybe it's a little "I'm used to it", but I
find the Swing UI much more convenient than the Development mode view:

- Clear tabs for Jetty and each browser window that comes up,
navigation is tricky in the Eclipse DMV tab
- Handy dandy "Launch in Browser" and "Restart Server" buttons
- Separate window and process makes it easy to see that I have it
running, close it to end the process, etc. In dev mode I have to
notice the tab, switch to it, and stop it from there to end to
process, not nearly as convenient. In this mode I often rerun app
only to find conflicting port because I didn't see and close the old
process.
- Separate window also doesn't compete with my code for space, makes
it easy to have a large log and still browse my code in my setup.
Personal preference, but hey.

The first two could just be improvements in the Eclipse DMV tab, but
don't assume everyone's workflow is improved through the "convenience"
of everything being built into eclipse!

jk

> > google-web-tool...@googlegroups.com<google-web-toolkit%2Bunsu...@googlegroups.com>
> > .

> > 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 google-we...@googlegroups.com.
> To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.

> For more options, visit this group athttp://groups.google.com/group/google-web-toolkit?hl=en.

[Rajeev Dayal]

On Fri, Apr 16, 2010 at 11:03 AM, kozura <koz...@gmail.com> wrote:

Ah thanks Rajeev, been looking for that, it works except you have to
set USE_REMOVE_UI=true.

 

Really? I'm glad it's working, but I think the right way to set it is to define an environment variable of "USE_REMOTE_UI" and set its value to "false". That should cause the Swing UI to pop up. Does that not work for you?

And since you asked...  Maybe it's a little "I'm used to it", but I
find the Swing UI much more convenient than the Development mode view:

 - Clear tabs for Jetty and each browser window that comes up,
navigation is tricky in the Eclipse DMV tab

Ah, are you saying that you'd prefer a different tab for each Jetty instance and browser window, instead of  having nodes in a Breadcrumb view? Note that you can switch the layout of the DMV - look at the view settings, and switch the layout to "Tree"

 

 - Handy dandy "Launch in Browser" and "Restart Server" buttons

The DMV also has the "Restart Server" button. We're working on making the URLs that pop up in the DMV launchable.

 

 - Separate window and process makes it easy to see that I have it
running, close it to end the process, etc.  In dev mode I have to
notice the tab, switch to it, and stop it from there to end to
process, not nearly as convenient.  In this mode I often rerun app
only to find conflicting port because I didn't see and close the old
process.
 - Separate window also doesn't compete with my code for space, makes
it easy to have a large log and still browse my code in my setup.
Personal preference, but hey.

Understood.

 

The first two could just be improvements in the Eclipse DMV tab, but
don't assume everyone's workflow is improved through the "convenience"
of everything being built into eclipse!

Thanks for the feedback - it is definitely useful!

[kozura]

It's definitely USE_REMOTE_UI=true to get the SWING UI, which
semantically makes sense anyway.. (yeah REMOVE was a type, fingers
faster than brain).

As for the rest, I'm sure I could fiddle with the devmode to fix some
of the navigation annoyances, but with my workflow the window works
much better for me in any case. I should just post issues, but it
would be nice to have the swing ui change to the new browser tab when
a new browser connects, and for scrolling to stay at the bottom of the
content..

Thanks
jk

> > <google-web-toolkit%2Bunsu...@googlegroups.com<google-web-toolkit%252Buns...@googlegroups.com>

[Rajeev Dayal]

Actually, after some more investigation, there is a bug here, which is why USE_REMOTE_UI=true is working. We'll have this fixed in the next version of GPE, but to make sure that you get the Swing UI, follow these steps:

-In your launch configuration, navigate to the Environment tab, and set USE_REMOTE_UI=false

-click back over to the Main tab

-apply your changes

-run the launch configuration

I know this seems like an odd workaround; it has to do with a bug in our logic for keeping the Arguments  tab in sync with changes in the launch config UI.

If you leave it as USE_REMOTE_UI=true, there is a chance that your launch config will flip back to using the Development Mode view.

[Christian Schuhegger]

On 16 Apr., 16:41, Rajeev Dayal <rda...@google.com> wrote:
> However, we'd be curious to know why you actually prefer the Swing UI to the
> Development Mode view :).

I use instantiations gwt designer plugin for eclipse and it has the
keyboard shortcut Shift+Alt+X G for launching the Swing UI and the gwt
application. I tried to figure out how to configure a similar shortcut
for the "Run As -> Web Application" but under "Window -> Preferences -
> General -> Keys" I was not able to find a Command that looks like
being the "Run As -> Web Application" action.

I would already be happy if I could get similar keyboard shortcuts
which I have with instantiations gwt designer and I don't need the
Swing UI.

Thanks,
Christian

[Christian Schuhegger]

On 16 Apr., 17:03, kozura <koz...@gmail.com> wrote:
> Ah thanks Rajeev, been looking for that, it works except you have to
> set USE_REMOVE_UI=true.

How did you find out so quickly that the parameter was called
"USE_REMOVE_UI" instead of "USE_REMOTE_UI"? I could not find that
parameter in any documentation? Did you search the sources?

By the way, for me the Swing UI opens if I set the parameter to
USE_REMOVE_UI=false.

Thanks,
Christian

[kozura]

Oh man I hope not, REMO*V*E was my typo heh. Maybe what you're seeing
is what Rajeev describes, where it doesn't grab the latest value
correctly. I just tried what he suggested and it seems that is
correct: USE_REMOTE_UI=false, but you have to switch to the main tab
and hit apply before running.

In any case I've just been happily using Java App instead of Web App
anyway which works fine for me!

On Apr 16, 12:38 pm, Christian Schuhegger