> To clarify, I want to use Localizer#getString(...) in a thraed I > create. > I have seen other posts on this issue, but haven't been able to figure > out the solution.
The Localizer.getString() looks for its messages in Wicket's property file structure, which depends on Application, the resource-oriented classes, hierarchies and so forth. Your best bet is to "pre-read" the values you need into a Properties object that you pass to the thread code. - Tor Iver --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
