Thanks Jurgen Eelco,
I understand you would not want this as default behaviour I suppose I can
figure it out.
Cheers,
Wilko
Eelco Hillenius wrote:
I see what you mean, and understand this use case may be good for some
occasions. There is a big danger however, of Wicket 'silently'
Hi Erik,
Wicket does fall back to the default *file* but what about the case where
you have one (or more) large properties file(s) for your default language
and you want to create a variation in which you want to change just a few
words for instance to make them more domain specific?
In that
Wicket does not only fall back to the default. It iterates over a long
list of property filenames which are created from the component tree,
locale, style and variation.
Juergen
On 4/8/07, Wilko Hische [EMAIL PROTECTED] wrote:
Hi Erik,
Wicket does fall back to the default *file* but what
I do understand this, but that is not really my question. Let's assume all
my keys are in an application scoped property file MyApplication.properties,
where MyApplication.java extends the WebApplication. Let this file contain a
large amount of keys. Now some customer of ours comes along and
Please take alook at Localizer and IStringResourceStreamLocator (?
hopefully I got it right). Localizer basically iterates of all
locators registers with Settings. Hence, you write and add as many new
locators as you like.
Juergen
On 4/8/07, Wilko Hische [EMAIL PROTECTED] wrote:
I do
I see what you mean, and understand this use case may be good for some
occasions. There is a big danger however, of Wicket 'silently' failing
(depending on your settings not throwing an exception or displaying a
place holder with a warning) when it cannot locate messages. It would
be too easy to
Right now, if I have a localized property file (e.g. Welcome_de.properties),
it seems I must have all resource keys defined in it.
I would prefer to have the localizer be smart enough to fallback to the
default properties file (e.g. Welcome.properties) if a property is not
present in the
It already does work like that.
http://cwiki.apache.org/WICKET/i18n-and-resource-bundles.html
Regards,
Erik.
dukejansen wrote:
Right now, if I have a localized property file (e.g. Welcome_de.properties),
it seems I must have all resource keys defined in it.
I would prefer to have the
