[TAPESTRY-1391] @EventListener method in component doesn't rewind the containing page's client-persistent properties

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.1.1
• Fix Version/s: 4.1.2
• Component/s: XHR/dhtml/Ajax
• Assignee: Jesse Kuhnert
• Reporter: John A. Gregg
• Created: 30/Mar/07 00:06
• Updated: 02/May/07 01:39
• Resolved: 02/May/07 01:39

Description

it appears that if a component has an event listener method which listens for events on objects within that component, but has parameters bound to values on the containing page, when that listener is invoked the component is rewound and its properties are updated – and propagated to the containing page, but that page has not been rewound at all with its own client-persistent properties. this causes all sorts of unexpected behavior where components are attached to completely random or uninitialized page objects.