tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] Closed: (TAP5-421) AjaxFormLoop event methods with context parameters are not called
Date Wed, 04 Mar 2009 19:21:56 GMT

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

Howard M. Lewis Ship closed TAP5-421.

    Resolution: Cannot Reproduce

I can see that this code change in July 2008 to address this need; it works, there are specific
tests to ensure that the AjaxFormLoop context parameter is propogated to the addRow event
handler method.

> AjaxFormLoop event methods with context parameters are not called
> -----------------------------------------------------------------
>                 Key: TAP5-421
>                 URL: https://issues.apache.org/jira/browse/TAP5-421
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.0.17
>            Reporter: Toby
>            Assignee: Howard M. Lewis Ship
> An AjaxFormLoop "onAddRow" is called, even if a context parameter is not set:
> public ValueHolder onAddRow() {
> }
> is called here:
> <tr t:type="AjaxFormLoop" t:source="valueHolders" t:value="valueHolder" t:encoder="encoder">
> ...
> But when a context parameter is passed:
> <tr t:type="AjaxFormLoop" t:source="valueHolders" t:value="valueHolder" t:encoder="encoder"
> ...
> public ValueHolder onAddRow(Category category) {
> }
> is not called.
> This prevents for example adding rows that depend on another selction (e.g. what kind
of field).
> In this case a Value rows which is selectable using a dropdown box  - but the values
to be displayed in this dropdown box should depend on the category that was selected when
"add row" is pressed.

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

View raw message