On Wednesday, 17 December 2025 at 7:03:18 pm UTC+11 Craig Mitchell wrote:
When debugging in Chrome, sometimes my breakpoints get hit on a page refresh, but the code is not executed (nor should it be).I reproduced the issue with the following:1. Create a sample project with https://github.com/NaluKit/gwt-maven-springboot-archetype:mvn archetype:generate -DarchetypeGroupId=com.github.nalukit.archetype -DarchetypeVersion=LATEST -DarchetypeArtifactId=modular-springboot-webapp(use any values, I just entered "a" for everything)2. Modify the a-client\src\main\java\a\App.java with the following:2.1 Add this static method:public static void delay(int delayMs, com.google.gwt.user.client.Command run) {
com.google.gwt.core.client.Scheduler.get().scheduleFixedDelay(() -> {
run.execute();
return false;
}, delayMs);
}2.2 In the MyHandler class onClick, call the static method:public void onClick(ClickEvent event) {
delay(1000, () -> {
sendNameToServer();
});
}3. Start it up:3.1: mvn gwt:codeserver -pl *-client -am3.2: mvn spring-boot:run -pl *-server -am4. Open it in Chrome: http://localhost:8080/5. Open the Chrome debugger, put a breakpoint on the line:delay(1000, () -> {6. Refresh the page. The breakpoint gets hit. It looks like this:It doesn't have a call stack, and if you try to step into it, it doesn't step into the delay method.Any idea why this occurs?
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/105e9a59-ebec-4355-996e-29095e8db22fn%40googlegroups.com.

No comments:
Post a Comment