Turns out I lied.  The debugger only seems to break in server code and
won't break in client code, most likely because of the module load
failure when using the debug URL generated.

So this appears to be a bug with the 2.0 RC1 debugger in some fashion,
as it relates to Eclipse or the browser plug-ins (though I get the
same error on FF 3.5 or IE 8).

--

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-tool...@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=.


Reply via email to