[KULRICE-10454] Improve handling of the binding errors Created: 11/Sep/13 Updated: 16/Jan/15
|Project:||Kuali Rice Development|
|Component/s:||Development, KNS Equivalency, User Experience (UX)|
|Security Level:||Public (Public: Anyone can view)|
|Reporter:||Jerry Neal (Inactive)||Assignee:||Unassigned|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
|KRAD Feature Area:||
|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.