Skip to content

Add support for discovering JPA 2.1 @Converter during scanning [SPR-10799] #15425

@spring-projects-issues

Description

@spring-projects-issues

Sinuhé opened SPR-10799 and commented

JPA 2.1 spec permits registering of converters using @Converter annotation. This works ok, at least in EclipseLink's last version. But it doesn't work with XML-free configuration using Spring. This is due to DefaultPersistenceUnitManager class, which scans specified packages looking for classes annotated with @Entity, @Embeddable and @MappedSuperclass, but not @Converter.

Just adding new AnnotationTypeFilter(Converter.class, false) to entityTypeFilters field worked for me.

private static final TypeFilter[] entityTypeFilters = new TypeFilter[] {
    new AnnotationTypeFilter(Entity.class, false),
    new AnnotationTypeFilter(Embeddable.class, false),
    new AnnotationTypeFilter(MappedSuperclass.class, false),
    new AnnotationTypeFilter(Converter.class, false)};

Affects: 3.2.3

Reference URL: http://eclipse.1072660.n5.nabble.com/Converter-not-being-picked-up-despite-having-autoApply-true-td161166.html

Issue Links:

Metadata

Metadata

Assignees

Labels

in: dataIssues in data modules (jdbc, orm, oxm, tx)type: enhancementA general enhancement

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions