Yes, I just set as you do, but it doesn't work. This is because what browser send through request header is US locale. Based on tapestry mechanism looking up for locale, it will search the nearest locale that is en. That why ordering like that doesn't work.
Any other idea ? Sorry forgot to mention, my tapestry version is 5.2.6. Thank you, Rendy. On Thu, Sep 8, 2011 at 5:59 PM, Taha Hafeez <tawus.tapes...@gmail.com>wrote: > I have not used it but I think the first locale in configuration > parameter tapestry.supported-locales( > SymbolConstants.SUPPORTED_LOCALES) is used as the default. > > So "in_ID,en" will make in_ID as default. > > Just a guess :) > > > On Thu, Sep 8, 2011 at 4:13 PM, Rendy Tapestry <rendy.tapes...@gmail.com> > wrote: > > Hi all, > > > > I build an application that will support two locale, that is in_ID and > en. I > > am using PersistentLocale to accomplish this and as consequences all my > > application url are encoded with selected locale (user set it manually > > through application menu). So if my application name is xyz and in_ID > locale > > is choosed, my url will: localhost:8080/xyz/in_ID/ > > If I directly access localhost:8080/xyz/ it will go to en locale because > my > > request header expecting US. What suppose I do to make in_ID the default > > locale if I access localhost:8080/xyz ? > > > > Thank you, > > Rendy. > > > > > > -- > Regards > > Taha Hafeez Siddiqi (tawus) > http://tawus.wordpress.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
