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


-- 
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.0-beta3 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta3/

Reply via email to