Btw, I would mind a decision about this in this weekend, as I'm finishing the chapter on localization right now :-)
FWIW, I don't like the silent failure we have now, and believe that using the body as a default isn't very helpful; e.g. if you have the default body the same as what you intended to put in the properties file for the default locale (which is something that I often do, and I can imagine other people doing that as well), and you make a spelling error in the key (of either the tag or in the properties file), you'd never notice Wicket not finding the property. Either outputting the key as the body or throwing an exception is way better imho. However, I wouldn't vote against people wanting to stick with the current pattern as it is quite late in the game to change this. Eelco On 11/3/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > On 11/3/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > > then you are violating the contract of wicket:message. if we do this > > then there is little point to allowing body inside wicket:message > > Erm, where is that contract defined? The body is for previewing. I > don't think I ever thought about this as a default, nor do I think we > should, since that is inconsistent with what we do elsewhere. > > Eelco > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
