On Tue, 19 Feb 2008, Federico Fanton wrote: > I see.. I'm trying this way too (alongside the Javascript one that > Igor Vaynberg pointed out), so I have a Map that maps every component > to its state, but I have a doubt.. How do you identify uniquely a > Component? I can't use getId() since I'm inside a repeater and every > component has the same id.. Right now I'm using getPath() and it works > quite well, but I don't know if it's the right choice, since I'm > refreshing the table with Ajax.. Do you store the component itself?
I think that we just stored the Component instances in that case, thogh you should be wary with that and especially with a repeater it might get difficult. A more dynamic way might be to use a marker interface for the relevant components and always check their states with a visitor. There again you should be careful with the repeater. However, for your form handling to work at all I suppose that the repeater items must not be recreated until the form is submitted or canceled anyway. Best wishes, Timo -- Timo Rantalaiho Reaktor Innovations Oy <URL: http://www.ri.fi/ > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
