You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2010/02/02 04:40:19 UTC
[jira] Updated: (TAP5-987) In some cases you can invoke
Form.recordError() and the Form will still fire a success (not a failure)
event
[ https://issues.apache.org/jira/browse/TAP5-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-987:
--------------------------------------
Summary: In some cases you can invoke Form.recordError() and the Form will still fire a success (not a failure) event (was: New ValidationTrackerWrapper somehow has changed behaviour of form validation)
> In some cases you can invoke Form.recordError() and the Form will still fire a success (not a failure) event
> ------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-987
> URL: https://issues.apache.org/jira/browse/TAP5-987
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.2.0, 5.2
> Reporter: Massimo Lusetti
> Assignee: Howard M. Lewis Ship
> Priority: Critical
>
> The changes introduced into r898476 to address TAP5-979 has introduced the new ValidationTrackerWrapper.
> This seems to cause a regression in the way form validation is processed.
> The old (and wanted) way is to have onValidate to check for form-wide validations and store into the form (form.recordErorr) any found violation. Then if there are violations (errors recorded) the form fire the onFailure events otherwise go to onSuccess.
> With this changes the event path goes always from validate to success events, the failure event is never fired.
> The only possible workaround is to have the onFailure event handler method to return an object (typically this) and never be of type void.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.