You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Thiago H. de Paula Figueiredo (JIRA)" <ji...@apache.org> on 2014/05/27 23:52:02 UTC

[jira] [Resolved] (TAP5-2247) AJAX Select could bubble up PREPARE event

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

Thiago H. de Paula Figueiredo resolved TAP5-2247.
-------------------------------------------------

    Resolution: Duplicate

Closing this one as a duplicate of TAP5-2301, even this one being older, because the other is better-written.

> AJAX Select could bubble up PREPARE event
> -----------------------------------------
>
>                 Key: TAP5-2247
>                 URL: https://issues.apache.org/jira/browse/TAP5-2247
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.4
>            Reporter: Geoff Callender
>
> Since 5.4, the Select model has to be regenerated server-side on submit (unless secure="literal:never"), else you'll fail with model bound to null. 
> If you're chaining AJAX Selects this is a pain - the workaround is to indiscriminately regenerate all of them in onActivate().
> Perhaps it would be better if each AJAX Select bubbled up a PREPARE event  so the container can prepare the appropriate model(s) before you handle VALUE_CHANGED.



--
This message was sent by Atlassian JIRA
(v6.2#6252)