On Fri, 13 Aug 2010 09:16:08 -0300, Inge Solvoll
wrote:
You have hit one of my problem spots in T5 :)
I also just use formState="iteration", because I simply don't understand
how to make the alternatives work...
Quick answer: it makes the form store information about the objects being
; in the loop. The
> second one seemed to made it work, even though I don't really understand
> why.
>
> formState="iteration" t:encoder="encoder">
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/Select-in-Loop-tp2471420
I made a ValueEncoder and also put formState="iteration" in the loop. The
second one seemed to made it work, even though I don't really understand
why.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Select-in-Loop-tp2471420p2572247.html
Sent from the
abelField="${currentAvailableBet}"
> > onChange="this.form.submit();"/>
> >
> >
> >
> >
> >
> >
> > All the selects get the value from the last select, something
;t
> want. I need them to all have their own independent values.
>
> Is there any way to make this happen?
>
> Thank you
>
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/Select-in-Loop-tp2471420p2471420.html
> Sent from the Tapestry -
On Tue, 10 Aug 2010 21:30:04 -0300, Mite wrote:
Hi
Hi!
I have the following loop containing two select components.
I guess you need to provide a ValueEncoder to the Loop's encoder parameter.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, de
