I have noticed that localization does not work for wicket when pages
versioning happens.
Let say I have three components in my page:
1. <wicket:message key="localizedResouceKey" />
2. new Label("contentNoModel", resolveLocalizedContent());
3. new Label("contentWithModel" , new Model() { getObect() {return
resolveLocalizedContent()}});
and also I have two links, which allows me to switch between two locales;
So, I enter the page and click between locale links many times. Then I click
back button several times.
Components 1. and 3. never gets localized, only component 2. which does not
use model got localized.
It looks like when older page version loads model does not update with new
locale value.
Is this a bug or expected behavior?
Quickstart project where we can reproduce specified behavior:
versionLocale.zip
<http://apache-wicket.1842946.n4.nabble.com/file/n4662260/versionLocale.zip>
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Wicket-localization-in-stateful-pages-tp4662260.html
Sent from the Users forum mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
