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 On Tue, Jun 2, 2009 at 11:03 PM, Greg <greg.ba...@gmail.com> wrote: > > 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 > > > --~--~---------~--~----~------------~-------~--~----~ 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-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
