Add facilities to translate ebean exceptions to Spring DataAccessException

[zero11-0203]

Hi all,

For better Spring integration, we could add an ExceptionTranslator to translate ebean exceptions to Spring DataAccessException like mybatis and jooq?

[rbygrave]

I'm not sure. What is the actual utility value of doing this?

Noting that Ebean has an exception hierarchy much like Springs (inspired by Springs data access exceptions and SQLException mapping in fact and works in a similar way with database platform specific mapping based on SQLState and errorCode obtained from the SQLException).

The mybatis exception translators are mapping from SQLException and that spring jooq one is as well. We don't have that case with Ebean which already has that SQLException mapping logic. So it's a different situation to the one with mybatis and jooq.

It isn't clear to me exactly why you want to map the ebean exception hierarchy to the spring one. The mapping of SQLException is a different thing / different case.

[zero11-0203]

Hi Rob,

Thanks for your quick reply.

Our team need to work with multiple persistence frameworks within the same application, and we encapsulate persistence code within Spring Repositories. If ebean provides an implementation for Spring's PersistenceExceptionTranslator, Spring will translate ebean exceptions thrown from repositories to Spring DataAccessException automatically, which will allow us to handle Spring DataAccessException uniformly in our application layer instead of handling different persistence framework specific exceptions.

[zero11-0203]

Maybe Hibernate would be a better example, which also has its own exception hierarchy.

[rob-bygrave]

Maybe Hibernate would be a better example, which also has its own exception hierarchy.

Maybe produce a Proof-Of-Concept with a spring repository using ebean and showing an exception being mapped?