Re: How Gwt runAsync decides to include code... be careful...?

Your compile report should tell you why your controller is now in the left over fragment. Its always hard to tell whats going on without knowing the whole code and the compile report.

For example a wild guess: In your second example you have two GWT.runAsync() calls with the same AsyncCallback (I assume that GWT.runAsync(callback) is a typo in your execute method and it should be GWT.runAsync(async)..). At first sight you have 2 possible paths now to load your controller. Maybe at the time the split points are calculated the GWT compiler has not yet optimized your IF statement to if(true) { .. } and pruned useless code and thus the CodeSplitter algorithm still sees two possible paths (although I think that its not the case, but I don't know the compiler flow).

-- J.

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/zxVHoeCpma0J.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.