Wicket localization in stateful pages

2013-11-10 Thread meduolis
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()

Re: Wicket localization in stateful pages

2013-11-10 Thread Sven Meier
Hi, your quickstart works fine: When you press the back button, the locale in the session stays on its last selection. Thus the dynamic localization in 1 and 3 stays on the current locale, while 2 show the previous locale, which was selected when the component was constructed. Regards Sven

Re: Wicket localization in stateful pages

2013-11-10 Thread meduolis
Exactly, I am really confused now. As I understand from your answer - this is expected behavior. I thought that back action should behave exactly the same when you navigating the site using wicket controls. Should I override back action somehow and do it myself? -- View this message in