The only way to handle exceptions thrown during (declarative) resource validation is via exception mappers. This mechanism may be insufficient in some cases, especially when an application (or framework) can recover from some errors. The problem is that there is a single mapper for say, ConstrainValidationException, for all resource methods in an application, making error recovery difficult.
The only way to handle exceptions thrown during (declarative) resource validation is via exception mappers. This mechanism may be insufficient in some cases, especially when an application (or framework) can recover from some errors. The problem is that there is a single mapper for say, ConstrainValidationException, for all resource methods in an application, making error recovery difficult.
Affected Versions
[2.0]