Hi, I was hoping to get the Localizer interface to be able to accept and translate based on Class in addition to Component.
Basically I have in my non wicket jar I'd like to have Country.java and Country.properties country.EN=England country.AU=Australia country.JA=Japan In wicket, I would be like to be able to access the properties through the Localizer and take advantage of the caching. At the moment the Localizer.getString(key, component, model, default) handles caching - and it would be great if it could do this for other classes. (Eg, Localizer.getString(key, clazz, default)) I could do this manually by a/ extending the localizer, and duplicating the cache code OR b/ implementing caching into a StringResourceLoader and exclude anything that is instanceof Component. Both of these feel ugly due to a/ duplication or b/ double handling of cache. Perhaps I've missed something in the javadoc. -- View this message in context: http://www.nabble.com/Localizer---reasonable-feature-request--tp16576843p16576843.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
