Hi Sven, Ah, that's the same kind of request. I can imagine that it's not a very hot feature. But we use the variant/style settings to override properties with kind of "theme" specific labels. But often such a theme only wants to use different naming for specific elements. With this option, we can simply override one property in a variant or style, and change a lot of labels all at once.
I thought actually that this was a default feature in the java ResourceBundles. But apart from that, I was expecting some feature like myapp.getResourceSettings().addResourceResolver(new MyCustomResolver()); but this doesnt seem possible. With such an option, we can implement this easily ourselves. Rob On Sat, Feb 21, 2015 at 4:37 PM, Rob Sonke <[email protected]> wrote: > Tobias, > > Somehow I'm missing your replies in gmail. But thanks for the suggestions. > Using custom models would be a last resort for me. Because I will have to > replace all occurences. I'm somehow hoping to hook into the localizer. > > On Sat, Feb 21, 2015 at 2:01 PM, Rob Sonke <[email protected]> wrote: > >> Hi all, >> >> I'm trying to achieve a fairly simple thing within .properties files to >> avoid a lot of duplicate words through different files. >> >> For example there's is a HomePage.properties with: >> lbl.foo=This is an example text, we love ${lbl.item} >> >> And then in MyWebApplication.properties: >> lbl.item=Wicket >> >> But as far as I can see, Wicket tries to resolve the parameters with >> objects passed to eg StringResourceModel. How can I hook into this and >> solve this in a nice way? >> >> Kind regards, >> Rob >> > >
