According to the source code your observation is correct. I've no good
reason why we implemented it this way.
Juergen
// Walk the component hierarchy down from page to the component
for (int i = searchStack.size() - 1; (i >= 0) && (string ==
null); i--)
{
Class clazz = (Class)searchStack.get(i);
// First check if a property with the 'key' provided by
the
// user is available.
string = loadStringResource(clazz, key, locale, style);
// If not, prepend the component relativ path to the key
if ((string == null) && (prefix != null) &&
(prefix.length() > 0))
{
string = loadStringResource(clazz, prefix + '.'
+ key, locale, style);
....
}
}
On 7/8/07, Kent Tong <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Just wondering why an unqualified resource key should take priority
> over a qualified one? eg, in a properties file:
>
> Required=The ${label} is missing!
> form.username.Required=You must provide your name!
>
> The first entry will take priority, while common intuition is that
> the first one is the default and the second one is overriding it.
>
> Thanks!
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Wicket-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/wicket-user
>
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
