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? -- Best regards, Gwyn mailto:[EMAIL PROTECTED]
