You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Geoff Callender (Updated) (JIRA)" <ji...@apache.org> on 2011/10/18 14:18:10 UTC
[jira] [Updated] (TAP5-1703) Remove need for @Persist with AjaxFormLoop

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

Geoff Callender updated TAP5-1703:
----------------------------------

    Description: 
Regarding use of a submitted AjaxFormLoop, ie. no database changes until submitted; I have almost succeeded in avoiding the need to use @Persist, but I still need @Persist to track the removal of original rows. 

You can see in this example that @Persist IS NOT needed to track added rows, nor removal of the added rows, but it IS needed to track removal of original rows:

    http://jumpstart.doublenegative.com.au/jumpstart/examples/ajax/formloop1 (true as of JumpStart 5.4.21)

Perhaps AjaxFormLoop could keep a list of the removed original rows in their encoded form and return it through a parameter on submit?

  was:
Regarding use of a submitted AjaxFormLoop, ie. no database changes until submitted; I have almost succeeded in avoiding the need to use @Persist, but I still need it to track the removal of original rows. 

You can see in this example that @Persist IS NOT needed to track added rows, nor removal of the added rows, but it IS needed to track removal of existing rows:

    http://jumpstart.doublenegative.com.au/jumpstart/examples/ajax/formloop1 (true as of JumpStart 5.4.21)

Perhaps AjaxFormLoop could keep a list of the removed rows in their encoded form and return it through a parameter on submit?

    
> Remove need for @Persist with AjaxFormLoop
> ------------------------------------------
>
>                 Key: TAP5-1703
>                 URL: https://issues.apache.org/jira/browse/TAP5-1703
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.2.6
>            Reporter: Geoff Callender
>
> Regarding use of a submitted AjaxFormLoop, ie. no database changes until submitted; I have almost succeeded in avoiding the need to use @Persist, but I still need @Persist to track the removal of original rows. 
> You can see in this example that @Persist IS NOT needed to track added rows, nor removal of the added rows, but it IS needed to track removal of original rows:
>     http://jumpstart.doublenegative.com.au/jumpstart/examples/ajax/formloop1 (true as of JumpStart 5.4.21)
> Perhaps AjaxFormLoop could keep a list of the removed original rows in their encoded form and return it through a parameter on submit?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira