You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Geoff Callender (Created) (JIRA)" <ji...@apache.org> on 2011/10/18 14:16:10 UTC
[jira] [Created] (TAP5-1703) Remove need for @Persist with
AjaxFormLoop
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 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?
--
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
[jira] [Updated] (TAP5-1703) Remove need for @Persist with
AjaxFormLoop
Posted by "Geoff Callender (Updated) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Resolved] (TAP5-1703) Remove need for @Persist with
AjaxFormLoop
Posted by "Geoff Callender (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Geoff Callender resolved TAP5-1703.
-----------------------------------
Resolution: Invalid
I've found a way to avoid @Persist to track removals. It will be in JumpStart 5.7.0 (to be released in a few days time).
Nonetheless, I think AjaxFormLoop would be much simpler to use if, on submit, it returned a list of the removed rows and a list of the added rows. After all, the client side knows exactly what you've done, so why should the server-side have to jump through hoops to figure it out? I'll raise an issue for that soon.
> 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
> 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
[jira] [Resolved] (TAP5-1703) Remove need for @Persist with
AjaxFormLoop
Posted by "Geoff Callender (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Geoff Callender resolved TAP5-1703.
-----------------------------------
Resolution: Invalid
I've found a way to avoid @Persist to track removals. It will be in JumpStart 5.7.0 (to be released in a few days time).
Nonetheless, I think AjaxFormLoop would be much simpler to use if, on submit, it returned a list of the removed rows and a list of the added rows. After all, the client side knows exactly what you've done, so why should the server-side have to jump through hoops to figure it out? I'll raise an issue for that soon.
> 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
> 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
[jira] [Updated] (TAP5-1703) Remove need for @Persist with
AjaxFormLoop
Posted by "Geoff Callender (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Geoff Callender updated TAP5-1703:
----------------------------------
Affects Version/s: 5.3
> 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.3, 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
[jira] [Updated] (TAP5-1703) Remove need for @Persist with
AjaxFormLoop
Posted by "Geoff Callender (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Geoff Callender updated TAP5-1703:
----------------------------------
Affects Version/s: 5.3
> 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.3, 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
[jira] [Updated] (TAP5-1703) Remove need for @Persist with
AjaxFormLoop
Posted by "Geoff Callender (Updated) (JIRA)" <ji...@apache.org>.
[ 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