[jira] [Updated] (TAP5-812) The input validation documentation incorrectly shows validation occuring in the success event handler method
[
https://issues.apache.org/jira/browse/TAP5-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Geoff Callender updated TAP5-812:
-
Affects Version/s: 5.3.2
The input validation documentation incorrectly shows validation occuring in
the success event handler method
Key: TAP5-812
URL: https://issues.apache.org/jira/browse/TAP5-812
Project: Tapestry 5
Issue Type: Bug
Components: documentation
Affects Versions: 5.3.2, 5.1.0.5
Reporter: Geoff Callender
Assignee: Howard M. Lewis Ship
Fix For: 5.2.0
The example in http://tapestry.apache.org/tapestry5/guide/validation.html has
to be fixed as a consequence of TAPESTRY-1972 .
Instead of this...
String onSuccess()
{
if (!authenticator.isValid(userName, password))
{
form.recordError(passwordField, Invalid user name or password.);
return null;
}
return PostLogin;
}
...it should be...
String onValidateForm()
{
if (!authenticator.isValid(userName, password))
{
form.recordError(passwordField, Invalid user name or password.);
}
}
String onSuccess()
{
return PostLogin;
}
--
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
[ 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
[ 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
