Read the Page Localisation section of Chapter 4 of the Developers
Guide for an explanation of why.
in fact, there it is - I did not realize that on first reading. However,
I still think it is an unnecessary restriction (rather, a bug). The
request MindBridge pointed us to already suggests a sol
From: Simon Robins <[EMAIL PROTECTED]>
Date: Wed Jan 15, 2003 7:12:13 pm Europe/London
To: Christian Sell <[EMAIL PROTECTED]>
Subject: Re: [Tapestry-developer] string-binding problem
You need to do this in the action that responds to the select
component when the locale is changed
erm, sorry, but I am not with you. Do you suggest this as a workaround
for the (otherwise quite simple) thing I am doing? And where do you
suggest this code to be located?
It still seems to me that this is more a case for the bugtracker than
for the FAQ. Correct me if I am wrong..
Simon Robin
Maybe this problem should be in the FAQ.
You need to do something like this:
IEngineService pageService =
cycle.getEngine().getService(IEngine.PAGE_SERVICE);
Gesture gesture = pageService().buildGesture(cycle, null, new String[]
{ getPage().getName() } );
throw new RedirectException(gesture.g
could somebody confirm that the issue described below is a bug? Should I
enter it into the bug tracker?
As it turns out, the only way to get around this is to change the
application design to be like the workbench demo, where after changing
the locale the user is directed to another page. If in
to answer my question regarding a workaround:
I tried this:
this forced the binding to be evaluated every time - BUT:
The string table for the component is created lazily based on the
current locale and cached afterward. It is NOT recreated if the locale
changes, and therefore wrong
Hello,
On one of my pages, I am using an Insert component with a string-binding
parameter. On the same page, I have a form with a Select component which
allows setting the Locale. After setting the locale, the same page is
redisplayed.
Now it turns out that when the locale is set, the Insert e
