[jira] Commented: (TAPESTRY-166) Allow Submits to defer invoking their listener

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

[jira] Commented: (TAPESTRY-166) Allow Submits to defer invoking their listener

JIRA tapestry-dev@jakarta.apache.org
     [ http://issues.apache.org/jira/browse/TAPESTRY-166?page=comments#action_64787 ]
Richard Lewis-Shell commented on TAPESTRY-166:


> Allow Submits to defer invoking their listener
> ----------------------------------------------
>          Key: TAPESTRY-166
>          URL: http://issues.apache.org/jira/browse/TAPESTRY-166
>      Project: Tapestry
>         Type: Bug
>   Components: Framework
>     Versions: 3.0
>  Environment: Operating System: All
> Platform: All
>     Reporter: Alex Ieong
>     Assignee: Howard M. Lewis Ship
>      Fix For: 4.0

> Quoted from the developer's guide (Chapter 6 , Services and forms):
> "The Form component doesn't terminate the rewind cycle until after all of its
> wrapped components have had a chance to render. It then notifies its own
> listener."
> But it doesn't seems to be the case. There are 2 PropertySelection components
> and 2 Submit components in the same Form component.
> When the Submit components are after the PropertySelection components,
> everything is ok.
> But when the Submit components are BETWEEN the PropertySelection components,
> the value in the later PropertySelection component is not assigned.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]