you are more then welcome to add an rfe, however it is not a simple fix. the cachekey currently contains a lot more information then just the propertykey and its all sandwiched into a single string, it contains the whole path. remember, in wicket components can inherit properties form their super class, as well as resolve properties based on locale, style, and variation.
to implement what you want we would have to break the string up into an object with multiple properties, then the clearcachekey() method would have to iterate over all cache keys and match any that use that property. -igor On Thu, Jul 23, 2009 at 1:13 PM, Mathias Nilsson<wicket.program...@gmail.com> wrote: > > maybe there should be methods to clear a part of the cache. > > Like getLocalizer().clearKey( key ); and getLocalizer.clearKeys( > List<String> keys ); > > > -- > View this message in context: > http://www.nabble.com/Localizing-thru-database-lookup-tp24627686p24633675.html > Sent from the Wicket - User 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 > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
