[KULRICE-10454] Improve handling of the binding errors Created: 11/Sep/13  Updated: 16/Jan/15

Status: Open
Project: Kuali Rice Development
Component/s: Development, KNS Equivalency, User Experience (UX)
Affects Version/s: None
Fix Version/s: 2.6
Security Level: Public (Public: Anyone can view)

Type: Bug Fix Priority: Critical
Reporter: Jerry Neal (Inactive) Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: Old
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
cloned from KULRICE-10452 Primary keys should not be editable o... Closed
cloned to KULRICE-10457 Automatic translation of person fields Open
discovered by KULRICE-10244 Maintenance Gap Analysis: basic stuff... Closed
Epic Link: Components
Rice Team: Framework
Rice Module:
KRAD Feature Area:
Application Requirement:
KAI Review Status: Not Required
KTI Review Status: Not Required
Code Review Status: Not Required
Include in Release Notes?:


When a request value cannot be converted to the underlying data type, Spring will thrown a binding exception. Currently, those are being caught by org.kuali.rice.krad.web.bind.UifBindingErrorProcessor. However, this needs to be reviewed (for one, should we be ignoring empty values?). Also, when binding errors are present, the request is contuining to the controller. We should be ending the request (could possibly do this in the interceptor preHandle by checking the message map).

In addition, the errors are not very helpful, they all state 'Field Label: Invalid Format'. There is information from the spring binding that can be used to give a better error message.

Generated at Sat Sep 26 08:54:49 CDT 2020 using JIRA 7.0.11#70121-sha1:19d24976997c1d95f06f3e327e087be0b71f28d4.