Hosted mode

[Kelo]

I created a web app with google plugin on Eclipse Ganymede 3.4, then I
made an entry on Debug Configurations... -> Web application. Running
on Hosted Mode, it didn´t stop on my breakpoints. After that I tried
including gwt-user.jar on Classpath - User Entries but I coudn't make
it works.

[Jim]

How about Debug As -> Web Application.

Jim
http://www.gwtorm.com
http://code.google.com/p/dreamsource-orm/

[Kelo]

I just tried by this way but I coudn´t make it stop on my breakpoints.

On 12 mayo, 12:04, Jim <jim.p...@gmail.com> wrote:
> How about Debug As -> Web Application.
>

> Jimhttp://www.gwtorm.comhttp://code.google.com/p/dreamsource-orm/

[Jason Essington]

Don't know what to tell you man, it is WoMM Certified*

[Ian Bambury]

I'd say you are lucky to even get the plugin to work. It's FOMM certified here (sorry, I don't have a clean image for that).

Ian

http://examples.roughian.com

2009/5/12 Jason Essington <jason.e...@gmail.com>

Don't know what to tell you man, it is WoMM Certified*

-jason

* http://www.codinghorror.com/blog/archives/000818.html

> --~--~---------~--~----~------------~-------~--~----~
> 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]

Hey,

You shouldn't need to include gwt-user.jar on your classpath; by virtue of selecting GWT when you create your new web application, a classpath container containing gwt-user.jar and gwt-dev-<your platform>.jar should be on your classpath automatically.

Where in your code are you setting your breakpoint (relative to onModuleLoad)?


Rajeev

[Greg]

I'm having the same problem as the OP. I'm working through the
StockWatcher tutorial, and I set breakpoints on the specified lines in
updateTable. Eclipse shows checkmarks on the breakpoint indicators
after the hosted-mode browser starts. Extra calls to GWT.log
demonstrate that control is passing through the marked lines, but
execution does not stop. Eclipse's perspective never changes to Debug.

OS: Vista
Eclipse v3.4.2 (Ganymede + EE)
GWT Plugin 1.0.1.v200905131143
GWT SDK for Win32 1.6.4.v200904062334
JDK 1.6.0_14

Thanks,
Greg

[Rajeev Dayal]

Hi Greg,

A few questions for you:

1) Are you using "Debug As" to launch your application's debugging session?
2) If you switch to the Debug perspective and look at the breakpoints view, are all of the breakpoints enabled?
3) If you go to Preferences (Window -> Preferences on Linux and Windows, Eclipse -> Preferences on Mac) -> Run/Debug and make sure that "Activate the workbench when breakpoint is hit" and "Activate the debug view when breakpoint is hit" options are enabled?
4) Can you tell me what is on your project's classpath?



Rajeev

[Kelo]

Hi Greg,
Push the button GWT Compile Project
Compile your project setting "log level" to Spam
Go to Debug Configurations , on the 2nd tab "GWT" of your project
set "log level" to Spam.
Run "Debug as..." ( your project )
Make your breakpoints on your project
Then press "Compile/Browse" on Hosted Mode
Once it fininshed press "Refresh" on Hosted Mode

On Jun 1, 4:19 pm, Rajeev Dayal <rda...@google.com> wrote:
> Hi Greg,
>
> A few questions for you:
>
> 1) Are you using "Debug As" to launch your application's debugging session?
> 2) If you switch to the Debug perspective and look at the breakpoints view,
> are all of the breakpoints enabled?
> 3) If you go to Preferences (Window -> Preferences on Linux and Windows,
> Eclipse -> Preferences on Mac) -> Run/Debug and make sure that "Activate the
> workbench when breakpoint is hit" and "Activate the debug view when
> breakpoint is hit" options are enabled?
> 4) Can you tell me what is on your project's classpath?
>
> Rajeev
>

[Steve]

I appears that the JDK v 14 is causing the problem. I installed the
v13 JDK and then told Eclipse (via the launch configuration) to use
v13 and breakpoints started to work again. I think this needs to be
reported back to GWT group.

Sincerely,
Steve

[Greg]

Rajeev Dayal wrote

> 1) Are you using "Debug As" to launch your application's debugging session?
> 2) If you switch to the Debug perspective and look at the breakpoints view,
> are all of the breakpoints enabled?
> 3) If you go to Preferences (Window -> Preferences on Linux and Windows,
> Eclipse -> Preferences on Mac) -> Run/Debug and make sure that "Activate the
> workbench when breakpoint is hit" and "Activate the debug view when
> breakpoint is hit" options are enabled?
> 4) Can you tell me what is on your project's classpath?

Thanks for your reply.

1) Yes, I'm launching the session with "Debug As."
2) Yes, breakpoints are enabled after switching to Debug perspective.
3) Yes, both checkboxes are checked.
4) GWT SDK 1.6.4 and jre6

Greg

[Greg]

Kelo wrote

> Push the button GWT Compile Project
> Compile your project setting "log level" to Spam
> Go to Debug Configurations , on the 2nd tab "GWT" of your project
> set "log level" to Spam.
> Run "Debug as..." ( your project )
> Make your breakpoints on your project
> Then press "Compile/Browse" onHostedMode
> Once it fininshed press "Refresh" onHostedMode

Thanks, this helped me make some progress! Eclipse caught the
breakpoint and switched to Debug perspective. I was able to step
around, inspect variables, and so on.

When I changed the code and saved, the hosted-mode browser stopped
responding to events. When I stopped and restarted the debugger,
breakpoints were again ignored. A couple of cycles of Compile/Browse
and Refresh got breakpoints triggering in Eclipse again. I tried
dialing the logging level back down but that left Eclipse aloof.

It's not elegant, but it's a workaround!

Greg

[Rajeev Dayal]

Hi,

I'm currently looking into this issue, and what I've found is that this problem is cropping up when using JDK 1.6.0_14. When using JDK 1.6.0_13, the problem does not seem to happen - all breakpoints are hit. So, as an alternate workaround, use a different JDK other than 1.6.0_14.

A bit more information - the problem seems to be specific to GWT, Eclipse, and JDK 1.6.0_14. I'm digging in deeper to try and figure out exactly who the culprit is.


Rajeev

[Rajeev Dayal]

Ok, we've dug deeper, and it seems like there is possible issue with Eclipse's debugger implementation, or bug in the JDK debugging system - it's hard to say which right now. A bug has been logged on Eclipse's bug tracker:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=279137

I'll ping this thread where there is a resolution on this issue.

[Greg Bacon]

Rajeev Dayal <rda...@google.com> wrote

> I'll ping this thread where there is a resolution on this issue.

Thanks for looking into it and for the additional workaround!

Greg

[Greg Bacon]

Rajeev Dayal <rda...@google.com> wrote

> I'm currently looking into this issue, and what I've found is that this
> problem is cropping up when using JDK 1.6.0_14. When using JDK 1.6.0_13, the
> problem does not seem to happen - all breakpoints are hit. So, as an
> alternate workaround, use a different JDK other than 1.6.0_14.

Workaround confirmed on Vista. Thanks again for chasing down the problem.

Greg

[Allan]

wow, it takes me a day! lucky, there is a way to do that. Thanks a
million!

On Jun 3, 4:14 am, Kelo <mcac...@gmail.com> wrote:
> Hi Greg,
>    Push the button GWT Compile Project
>    Compile your project setting "log level" to Spam
>    Go to Debug Configurations , on the 2nd tab "GWT" of your project
> set "log level" to Spam.
>    Run "Debug as..." ( your project )
>    Make your breakpoints on your project
>    Then press "Compile/Browse" on Hosted Mode
>    Once it fininshed press "Refresh" on Hosted Mode
>
> On Jun 1, 4:19 pm, Rajeev Dayal <rda...@google.com> wrote:
>
> > Hi Greg,
>
> > A few questions for you:
>
> > 1) Are you using "Debug As" to launch your application's debugging session?
> > 2) If you switch to the Debug perspective and look at the breakpoints view,
> > are all of the breakpoints enabled?
> > 3) If you go to Preferences (Window -> Preferences on Linux and Windows,
> > Eclipse -> Preferences on Mac) -> Run/Debug and make sure that "Activate the

> > workbench whenbreakpointis hit" and "Activate the debug view when
> >breakpointis hit" options are enabled?