yes, you can subclass a page and put the resource next to it. another alternative is to put the package into the same package as the original page. yet another alternative is to add those keys to your myapplicaiton.properties
-igor On Feb 12, 2008 7:49 AM, Wang, Yuesong <[EMAIL PROTECTED]> wrote: > Maybe you can extend the page, or duplicate the external package in your > own code base, and put your localized properties file there? WARNING: > I'm a newbie to wicket, so my suggestions might not work at all ;) > > Yuesong > > > -----Original Message----- > From: Thomas Kappler [mailto:[EMAIL PROTECTED] > Sent: Tuesday, February 12, 2008 9:32 AM > To: [email protected] > Subject: Override external .properties for localization > > Hi, > > my question seems trivial, but I just can't find anything: how to > localize a page or panel that's not my own, but is in a referenced > library (like Wicket itself)? For instance, I'd like to have a German > version of UserAdminPage in databinder (which provides String > resources), so I would write a UserAdminPage_de.properties, but where > should I put it and what do I have to do so that it's picked up and > used? > > Thanks, > Thomas > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
