Christian Thanks, I'll give that a shot. That sounds much easier, and I hadn't even considered it!
Gareth ----- Original Message ---- From: Christian Haselbach <[EMAIL PROTECTED]> To: Tapestry users <users@tapestry.apache.org> Sent: Monday, 16 October, 2006 2:14:57 PM Subject: Re: For component ConcurrentModificationException during rewind. Zitat von Gareth <[EMAIL PROTECTED]>: > I have gotten around the problem by, in the listener for "onDelete", I flag > the row for deletion, and then in the "PageBeginRender" method, I check to > see that it is not rewinding - i.e. it is about to start rendering the > response, and if the deletion flag is set, remove the corresponding row. You could use the "action" parameter instead of the "listener" parmeter in the submit component. This should be called after the loop has been rewinded. See http://tapestry.apache.org/tapestry4/tapestry/ComponentReference/Submit.html Or you could create a new list, initialized with the original list, to run the for loop. This might be expensiv, depending on the size of the list. Regards, Christian --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Send instant messages to your online friends http://uk.messenger.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
