You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tapestry.apache.org by "Jesse Kuhnert (JIRA)" <de...@tapestry.apache.org> on 2007/05/02 03:41:15 UTC

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

     [ https://issues.apache.org/jira/browse/TAPESTRY-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jesse Kuhnert resolved TAPESTRY-1391.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 4.1.2
         Assignee: Jesse Kuhnert

> @EventListener method in component doesn't rewind the containing page's client-persistent properties
> ----------------------------------------------------------------------------------------------------
>
>                 Key: TAPESTRY-1391
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1391
>             Project: Tapestry
>          Issue Type: Bug
>          Components: XHR/dhtml/Ajax
>    Affects Versions: 4.1.1
>            Reporter: John A. Gregg
>         Assigned To: Jesse Kuhnert
>             Fix For: 4.1.2
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org