nevermind, it does work like #2.

-Igor


On 1/25/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
i was looking at retrofitting the wicket message resolver back to 1.1 and i noticed that currently if the key is not found an empty string is used by default. what this does is effectively remove the message from markup entirely if the key is not found.

there are a couple of alternative behaviors we can implement:
1) add a warning tha the resource is not found like we do when other resources are not found

2) leave the body of the tag if the resource is not found

imho 2 is the best because it allows you to not have as much stuff in property files for your default locale.

leave it as it is or go with 1 or 2?

-Igor


Reply via email to