On Thu, 15 Jul 2010 10:56:03 -0300, Adam Zimowski
wrote:
So I *could* do it like this with Tapestry by extending Tapestry's
filter, but that's not in the spirit of Tapestry. Furthermore, the
framework is famous for making things amazingly simple. I think I'm
missing something. What is it?
Y
It seems to me that neither PersistentLocale nor LocalizationSetter
truly force desired locale for the request. After implementing
solution suggested here, I'm still exhibiting undesired bahavior, that
is stripping locale from the URL makes tapestry use browser's locale,
not the one I have forced.
On Wed, 14 Jul 2010 13:36:50 -0300, Adam Zimowski
wrote:
@Persist
private String language;
You should use @SessionState instead and then use the
ApplicationStateManager to read or set it.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, deve
er
wrote:
> Thanks a lot, Juan and Thiago!
>
> We'll try to implement this idea... :)
>
>
>
>
>
> De: Juan E. Maya
> Para: Tapestry users
> Enviadas: Quarta-feira, 18 de Novembro de 2009 16:25:55
> Assunto: Re: Request to a u
:) u r right tiago! It should a RequestFilter :) My memory betrayed me :)
On Wed, Nov 18, 2009 at 7:06 PM, Thiago H. de Paula Figueiredo
wrote:
> Em Wed, 18 Nov 2009 15:53:32 -0200, Juan E. Maya
> escreveu:
>
>> U can store the locale of the user in a cookie or in db (if u already
>> have a sess
Em Wed, 18 Nov 2009 15:53:32 -0200, Juan E. Maya
escreveu:
U can store the locale of the user in a cookie or in db (if u already
have a session) and then set the desired locale in a
ComponentRequestFilter. It would be something like this:
Nice implementation, but why a ComponentRequestFilte
Hi Everton,
U can store the locale of the user in a cookie or in db (if u already
have a session) and then set the desired locale in a
ComponentRequestFilter. It would be something like this:
public class LocaleComponentRenderRequestFilter implements
ComponentRequestFilter {
private fina
