Wednesday, December 21, 2016

Re: Force Client Bundle to refresh without any modification on the file


Thanks for the reply :). Yes that's the solution I selected, it's just sad that it won't work "magically" (and require adding a line in resources), but I guess it's not that bad. I didn't think about the code pruning issues, good catch.

About GWT generators not being supported anymore, does this include the ClientBundle? The generators I overridden (AbstractResourceGenerator) is heavily used in ClientBundle (like for TextResource etc..), and I didn't think they were going to remove that.

On Wednesday, December 21, 2016 at 7:27:16 PM UTC+1, Jens wrote:

Is there a solution to tell GWT that my ClientBundle needs to be refreshed at every compilation?

No. Also your solution defeats any code pruning because of the generated switch statements that references all the component templates that might or might not be used by a given application.

You should provide a predefined ClientBundle that has one method per component that returns the matching TemplateResource. Your library users would then create their own ClientBundle for their own templates or use the default ones. Basically it's very much like defining lots of ImageResource methods on a ClientBundle to provide images in an optimizable way.

Also if you want your library to work in a post GWT 2.8 world, then you might want to consider an APT based solution as GWT 3.0 will likely not support GWT generators anymore. 

-- 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