- All Known Subinterfaces:
- All Known Implementing Classes:
- Functional Interface:
- This is a functional interface and can therefore be used as the assignment target for a lambda expression or method reference.
This allows consistent usage of combined exception translation functionality, without forcing a single translator to understand every single possible type of exception.
- Rod Johnson, Juergen Hoeller
translateExceptionIfPossibleTranslate the given runtime exception thrown by a persistence framework to a corresponding exception from Spring's generic
DataAccessExceptionhierarchy, if possible.
Do not translate exceptions that are not understood by this translator: for example, if coming from another persistence framework, or resulting from user code or otherwise unrelated to persistence.
Of particular importance is the correct translation to DataIntegrityViolationException, for example on constraint violation. Implementations may use Spring JDBC's sophisticated exception translation to provide further information in the event of SQLException as a root cause.
ex- a RuntimeException to translate
- the corresponding DataAccessException (or
nullif the exception could not be translated, as in this case it may result from user code rather than from an actual persistence problem)
- See Also: