1) breaking shouldn't: in tools > options > misc > java debugger > step filters, have "do not step into" set synthetic methods (checked), static initializers (checked), , added entries classes matching java.*, java.util.abstractexecutorservice, , java.util.threadpoolexecutor (redundancy in pursuit of overkill).
despite this, debugger breaks @ java.util.concurrent.threadpoolexecutor$worker.run(). have tried both "step through filters reach unfiltered code" checked , cleared.
2) not breaking should: in gwt mvp project, have set breakpoints in presenter, , no longer trip (used to). server rpc breakpoints trip fine, , don't see changes cause changes in way client side code treated. fwiw, have gwt4nb plugin installed & activated.
any ideas on problems behind these behaviors?
update: seems netbeans doesn't using gwt version 2.2. following in pom...
<gwt.maven.plugin.version>2.2.0</gwt.maven.plugin.version> <gwt.version>2.2.0</gwt.version> ...the project -> properties -> frameworks doesn't show gwt. if manually add gwt, adds following nodes project properties (oddly, not replace existing gwt version node):
<gwt.version>2.0.3</gwt.version> <runtarget>welcomegwt.html</runtarget> the project properties dialog doesn't offer configuration options gwt framework. still haven't found way 2.2.0 stick, , think contributing client-side debugging problem.
the typical problem code being stepped through (compiled) code not match source code in project. if update source code , save it, , step through deployed project in debugger, can produce same behavior.
Comments
Post a Comment