Re: Why changing text in properties file (using ConstantsWithLookup) doesn't make any change in the constants in Production Mode?

Does "dynamic i18n" make the app run slower?

On Saturday, March 8, 2014 9:07:34 PM UTC+11, Thomas Broyer wrote:

As I said elsewhere, this is because the strings are compiled into the JavaScript.

What you want is "dynamic i18n": http://www.gwtproject.org/doc/latest/DevGuideI18n.html#DevGuideDynamicStringInternationalization

(this is much less powerful than static i18n though)

On Saturday, March 8, 2014 3:49:37 AM UTC+1, Tom wrote:

Here is my problem. I want to change the Constants dynamically for my web app when it's already in the Production Mode.

So here is what I did

import com.google.gwt.i18n.client.ConstantsWithLookup;  public interface MyConstants extends ConstantsWithLookup{     String email();  }  

In the MyConstants.properties file

email=My email  

Now i compiled the whole project & deploy it into server. At first test in server, it showed correctly "My email", then I went to C:\tomcat\webapps\myApp\WEB-INF\classes\myApp\client\MyConstants.properties & change the text in that file to:

email=Your email  

Now i ran myApp in tomcat but nothing happened. It still uses the My email String rather than Your email string.

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.