Henri,
Thanks for your reply. Actually I had some lazy binding session exceptions
but they disappered when I applied the keyExpression attribute according to
Jesse's tip!
I've looked several times at Tapernate but each time I've desided it's too
much work to get on track. And my small app is no
Thank you! That was really simple - and it works :)
One golden star to you, Jesse.
Malin
On 7/26/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
Use the "keyProvider" parameter. It will do wonders for your client
persisted form properties :)
On 7/25/06, Malin Ljungh <[EMAIL PROTECTED]> wrote:
>
On 7/25/06, Malin Ljungh <[EMAIL PROTECTED]> wrote:
Hi all,
I've been using Tapestry for weeks and today I for the first time did
a "View page source"
in my browser... and I was a little surprised. In one of my pages I'm
looping
a Set using a For component to display some entities in a table. T
Use the "keyProvider" parameter. It will do wonders for your client
persisted form properties :)
On 7/25/06, Malin Ljungh <[EMAIL PROTECTED]> wrote:
Hi all,
I've been using Tapestry for weeks and today I for the first time did
a "View page source"
in my browser... and I was a little surprised.
