You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since Spring 6.0 the method is marked as deprecated, removal is planned for 6.1.
I tried to override handleMethodArgumentNotValid Method, but that has no impact.
For example if several arguments are not valid, then a BindException is thrown instead
How can I deal with this problem, so that my solution works with the next upgrade?
The text was updated successfully, but these errors were encountered:
It looks like there is one more place in ModelAttributeMethodProcessor that wasn't switched to use MethodArgumentNotValidException as part of #29251. Could you confirm that the BindException you're seeing is raised from here?
rstoyanchev
changed the title
How to handle a BindException in Spring 6
BindException raised instead of MethodArgumentNotValidException subclass
Mar 10, 2023
In our application we override handleBindException from ResponseEntityExceptionHandler to improve the output of error message.
Since Spring 6.0 the method is marked as deprecated, removal is planned for 6.1.
I tried to override handleMethodArgumentNotValid Method, but that has no impact.
For example if several arguments are not valid, then a BindException is thrown instead
How can I deal with this problem, so that my solution works with the next upgrade?
The text was updated successfully, but these errors were encountered: