O'Reilly logo

GWT in Action, Second Edition by Adam Tacy, Robert Hanson, Jason Essington, and Anne Tökke

Stay ahead with the world's most comprehensive technology and business learning platform.

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, tutorials, and more.

Start Free Trial

No credit card required

19.2. Using the Compile Report

Throughout the book, we’ve talked a lot about how the compiler generates a bunch of code for you, prunes out any code that isn’t called, creates several versions of that code specific to each browser, runs it through a Java-to-JavaScript conversion process, and then spits it out. You can dismiss it as magic, but dismissing it won’t help you understand what’s in there (and what isn’t).

Understanding the output is useful for a number of reasons. Perhaps you want to reduce the size of your compiled code and need to know what classes have been compiled into the output. Perhaps your users are complaining about a JavaScript error in a function named Cb, and you need to know to what Java method it corresponds. Or maybe ...

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, interactive tutorials, and more.

Start Free Trial

No credit card required