[TAP5-1896] AjaxFormLoop corrupts list when redisplayed after Remove then server-side failure

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Won't Fix
• Affects Version/s: 5.3, 5.2
• Component/s: tapestry-core
• Assignee: Unassigned
• Reporter: Geoff Callender
• Created: 04/Apr/12 09:09
• Updated: 24/Jul/13 22:56
• Resolved: 24/Jul/13 22:56

Description

To see the effect use an AjaxFormLoop with input field(s) and at least 3 rows built from existing data. It must be in a Form.

Remove row n.
Submit, ensuring in some way that you get a server-side validation error.

The redisplayed loop will have all the right output values, but the input values will be corrupted:

• the removed row will be missing (good),
• row n+1 will be correct (good),
• every row below that will have input values that belong to the row before it (bad).

If you try the process again but this time remove 2 adjacent rows you'll get:

• the removed rows (n-1 and n) will be missing (good),
• row n+1 will be correct (good),
• row n+2 will be correct (good),
• every row below that will have input values that belong 2 rows before it (bad).

Issue Links

• is part of: TAP5-280 Fields injected by AjaxFormLoop sometimes have incorrect values after submits where validation fails.