Monday, November 21, 2016

Re: GWT Code Splitting: The GWT Stuff and My Core Java Classes

Can someone clarify?

Each GWT module that has an EntryPoint defined will end up being a GWT application. Each GWT application will contain the code of the GWT SDK that you are using in your app, e.g. a GWT Button, Label, LayoutPanels, etc. So yes if you have 10 small, independent GWT applications (= 10 entry points) and you sum up their final JS size you will end up with a larger total download compared to a single GWT application (= 1 entry point) containing the modules.

So people generally end up using a single GWT application (entry point) and if their app becomes too large they use code splitting so that the app is downloaded in smaller chunks on demand. However some people are also fine with having 10 GWT applications. Server side GZ compression, client side caching and the fact that each of the 10 GWT applications can also use code splitting makes the overhead of duplicated GWT SDK code downloads not that important. With 10 applications you also get benefits like updating them independently from each other.

So again: No you can not have a GWT.js library shared across your GWT modules. You either have to create a single GWT application or multiple GWT applications. A single GWT application will always be smaller than the same application split up into 10 smaller GWT applications because of GWT SDK code duplications. Choose whatever fits best for your use case.

-- J.

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
To post to this group, send email to
Visit this group at
For more options, visit

No comments:

Post a Comment