> Yes, you're right. Our problem occurs when we try to do some > locale-related stuff, i.e.: > > Locale defaultLocale = > Application.get().getApplicationSettings().getDefaultLocale(); > getSession().setLocale();
ApplicationSettings#defaultLocale was removed a while ago as the default implementation of returning Locale.getDefault() was very naive (you deploy on another server, and you could suddenly have a locale change) and also because that method didn't solve anything in the first place. I know it's not related to your problem, but the 1.3 way of fixing a locale is to just create a custom Session object and set the locale in the constructor. Eelco ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
