That might be a solution for some cases, yes.
This is my actual problem, more specific: I have a dropdown with the
values 1 to 50. If the user selects 30, there should be 30 text input
fields on the page.
This, I think, cannot be solved by an if/else test like FormConditional,
because it performs iteration based on a dropdown value. And tapestry
throws an exception when it finds that the number of input elements does
not match the internal list anymore...
Inge
Pedro Abelleira Seco wrote:
How about using a Conditional (FormConditional, of course) and show the
input field or a Hidden depending on the condition?
El Xov, 17-11-2005 a las 13:53 +0100, Inge Solvoll escribió:
T3 question:
I have several pages where I have the following problem:
When i select a value in a dropdown, it should change the form on the
page by adding an input field, or removing some other input fields. But
if I do this without redirecting, I get stale link exceptions because
tapestry doesn't have control over the components on the page any more.
Is there another solution than making the needed page properties
persistent and redirecting when the number of components on the page
changes on submit?
Cheers
Inge
---------------------------------------------------------------------
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]
