there is only one correct way to clear the cache, so i do not see why that needs to be externalized.
-igor On Thu, Jul 23, 2009 at 3:47 PM, Mathias Nilsson<wicket.program...@gmail.com> wrote: > > Yes I get you point. > > What about assigning clearing strategies that can be added and implemented. > let's say it's sufficient for me to just clear the cache if the component is > not a subclass of another component. I can implement my own strategy for > clearing the cache or key/keys. > > ClearCacheStrategy // clears entier cache > ClearNonInheritedKeyStratergy // > > And so on. > > But i guess the price to pay of clearing the whole cache and hitting the > database again is a nice price to pay without spending time on this. > -- > View this message in context: > http://www.nabble.com/Localizing-thru-database-lookup-tp24627686p24635970.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
