Localization properties overriding

2010-01-25 Thread Marek Šabo
Hi all, I have a question regarding property binding when using localized property files, consider following: UserHomePage page has one property for localization and that is title=User's Home which is then used in markup as: head titlewicket:message key=title //title /head ... This page

Re: Localization properties overriding

2010-01-25 Thread Marek Šabo
Hi Erik, I understand this - I use it eg. HomePage has title=Home, UserHomePage has title=User's Home etc... and it works top-down as expected. But why does this topmost property title, that should bind itself to key=title of wicket:messages attached to page component itself, got bounded to

Re: Localization properties overriding

2010-01-25 Thread Erik van Oosten
The search for any given property key is top-down, the first result is found. Why? As I said, to allow an override of the component (which may be third party). Regards, Erik. Marek Šabo wrote: Hi Erik, I understand this - I use it eg. HomePage has title=Home, UserHomePage has

Re: Localization properties overriding

2010-01-25 Thread Marek Šabo
Hi, well I see where was the misunderstanding. The FIRST result found. What I'm used to when going from top to down is the LAST definition takes effect. Well maybe I will see to it when I will do some modules but for now I'll just rename it and won't use single name properties anymore to