Possibly, although it does allow you to see on the rendered page just what properties didn't get found, rather than just the log file!
Mainly though I'm concerned about trying to find out if I'm missing something or have we really got unreachable code in WicketMessageResolver? /Gwyn On Wednesday, September 26, 2007, 12:41:58 PM, Martijn <[EMAIL PROTECTED]> wrote: > I think the proper use should be: > <wicket:message key='xxx'>Default value</wicket:message> > Where the default value would be rendered if no message bundle was found. > Providing a key inside the tags is not very intuitive IMO. > Martijn > On 9/26/07, Gwyn Evans <[EMAIL PROTECTED]> wrote: >> Anyone got a couple of mins to check WicketMessageResolver? >> >> It looks to me as if >> WicketMessageResolver$MessageLabel.onComponentTagBody() >> would support >> >> <wicket:message>key</wicket:message> >> >> albeit with a debug warning, by using 'key' as the key, but it >> doesn't, as before it gets to that part of the code, it's been >> intercepted by an earlier trap in resolve() that throws >> MarkupException( "Wrong format of <wicket:message key='xxx'>: >> attribute 'key' is missing"); >> >> Any thoughts as to what the correct behaviour should be?
