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] Assigned: (TAP5-987) New ValidationTrackerWrapper somehow has changed behaviour of form validation
Date Tue, 02 Feb 2010 02:58:20 GMT

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

Howard M. Lewis Ship reassigned TAP5-987:
-----------------------------------------

    Assignee: Howard M. Lewis Ship

> New ValidationTrackerWrapper somehow has changed behaviour of form validation
> -----------------------------------------------------------------------------
>
>                 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.


Mime
View raw message