Thanks, I think extending or writing my Localizer would be the path to go.
* Rolling my own cache that gets the key from the primary key in the database. * If an administrator updates a value then I can delete the primary key from the cache. And force a roundtrip to the database. -- View this message in context: http://www.nabble.com/Localizing-thru-database-lookup-tp24627686p24644843.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
