Sure thing. My displaytag.properties file contains the following two relevant entries:
locale.resolver=org.displaytag.localization.I18nStrutsAdapter locale.provider=org.displaytag.localization.I18nStrutsAdapter Todd -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Srepfler Srgjan Sent: Wednesday, April 05, 2006 8:16 AM To: [email protected] Subject: Re: [displaytag-user] I18n in DisplayTag w/Struts Farmer, Todd wrote: > Indeed, there was a simple explanation. I needed both the > locale.resolver and locale.provider keys in my displaytag.properties > file - I only had the former. > > Todd Farmer > > > > Can you please post here what did you set the keys to? I'm getting some errors with it so I would like to see if what I'm doing is wrong. Thanks Srgjan ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ displaytag-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/displaytag-user ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ displaytag-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/displaytag-user
