JPA Mapping limitations

There are 2 known JPA mappings that Ebean does not support.


Only single table inheritance is supported.

There is no planned support for JOINED or TABLE PER CLASS inheritance strategies.


Only a single type converter per type is supported.

JPA @Converter autoApply false is not honoured. This means that we expect a type to be mapped consistently for all properties that it is used. For example, we can't have to Converters mapping Boolean two different ways in the same Ebean database instance.

Refer to github issues marked with the Limitation tag.