Doh! Found it - didn't dig deep enough. Thanks!
So the string that is required in the constructor is simply ignored if I
supply an overridden newHeader - it looks like I should be able to use
'null' there without ill effects. I'm curious though: is there a reason
why the constructor wouldn't
all you had to do was look at the source. its not that difficult to do...
new propertytreecolumn(...) {
public component newhreader(parent, id) {
label l=super.newheader(parent,id);
l.setdefaultmodelobject(getstring(l.getdefaultmodelobjectasstring());
}
}
-igor
On S
Anyone have any hints/tips/wiki page references, or are column headers
really not internationalizable?
Thanks,
Doug.
DCarr wrote:
Hi,
Is there a recommended way to set the header string in a
PropertyTreeColumn when that string should come from a resource file?
It doesn't take a model, s
Hi,
Is there a recommended way to set the header string in a
PropertyTreeColumn when that string should come from a resource file?
It doesn't take a model, so the load cannot be deferred until later;
using getLocalizer().getString(...) results in:
-WARN::org.apache.wicket.Localizer: T