[TAP5-1332] In a multi-zone update, if the referenced Zone can not be found on the client, Tapestry stops updating Zones with no error

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.2.2
• Fix Version/s: 5.2.3
• Component/s: tapestry-core
• Assignee: Howard Lewis Ship
• Reporter: Howard Lewis Ship
• Created: 03/Nov/10 01:17
• Updated: 10/Nov/10 21:37
• Resolved: 05/Nov/10 20:43

Description

In other words, if the server specified the id of an element that doesn't exist, an exception is thrown (aborting updates of all other zones) but the exception is not reported.

Tapestry should use the console to display the error ("Zone 'xyz' could not be located.') and continue with the remaining zones.