Hi I just found out that this issue should be fixed in wicket 1.3.0 beta 4 (wicket-issue 936). Where can I get that? Which is the current release, best suited for a production environment? Thanks!
Marcus 2007/10/2, marcus dickerhof <[EMAIL PROTECTED]>: > > So, > I looked at the sources of Localizer, > for "Tried to retrieve a localized string for a component that has not yet > been added to the page. " which is the warning i get. > > In this case the Localizer calls loader.loadStringResource(component, > key); without passing a locale. That's why I always get the german text :-) > Sorry! > But now how can I avoid this "component that has not yet been added to the > page." problem? > When I use a wicket:message tag, do I also have to add that message to the > page-tree in my Java class manually? > > Thanks > Marcus > > > > > 2007/10/2, marcus dickerhof < [EMAIL PROTECTED]>: > > > > Hi Cristina, > > thanks for your reply. > > The problem is, that the session locale is changed, but somehow > > there seems to be another locale present which is then passed to the > > IStringResourceLoader.loadStringResource implementation. > > Have you got any ideas? > > > > Thanks a lot > > Marcus > > > > 2007/10/2, Cristina < [EMAIL PROTECTED]>: > > > > > > > > > Hi Marcus, > > > > > > > > > marcus dickerhof wrote: > > > > > > > > [...] > > > > Question: Can it be, that the Session-Locale is not used, because of > > > the > > > > Localizer-Problem? Which locale is used instead? > > > > > > > > > > If you're setting the Locale in your Session (probably a class that > > > extends > > > WebSession) and then getting the Locale through the Session, the > > > warning > > > about the Localizer doesn't mean, as far as I know, that the Session > > > Locale > > > isn't being used. Otherwise, the default Locale, which is defined by > > > your > > > browser settings, will be used. > > > > > > > > > marcus dickerhof wrote: > > > > > > > > Is there a better way to get database-resource-strings? > > > > > > > > > > I believe .properties files are a better way to get localized > > > strings... Is > > > there any reason why you can't/shouldn't use them? > > > > > > Hope this helps, > > > > > > Cristina > > > > > > -- > > > View this message in context: > > > http://www.nabble.com/Newbie-Question-Loading-localization-Resources-from-Database-tf4548742.html#a12990188 > > > > > > Sent from the Wicket - User mailing list archive at Nabble.com. > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > >
