Via a test that made no sense at all, I just discovered this issue.

To recap: Hibernate has, AFAICT, never respected the use of @AttributeOverride on a subclass in an entity hierarchy. (It can be usefully used when inheriting a @MappedSuperclass.)

So the request in this issue was to not throw an exception but instead just log a warning and just ignore the annotation.

This is a terrible idea and incredibly hostile to users.

I am now changing Hibernate to throw the exception it should always have thrown.

Fixed in 5.3 branch as well.

Hi @GailBadner, no in 5.2.x the @AnnotationOverride had no effect. Then in 5.3.x it started throwing exception. This ticket tackles the exception. Shall I raise another one for the AnnotationOverride not working, or can we address it here?

The problem is that I'll have to convince the Log4J team the change is necessary, even though it works with Hibernate versions earlier than 5.4 and with Eclipselink, and it will takr a very long time to get a release with such changes 😟
I really was hoping to be able to switch to Java 11 soon.

, I understand that no exception was thrown in 5.2. Did an @AttributeOverride actually work properly when mapped on an entity class in a TABLE_PER_CLASS hierarchy? It would help a lot if you could add a test case to your PR that shows that it is actually working (overriding the column name) with your fix.

, According to the spec, @Inheritance(...) "is specified on the entity class that is the root of the entity class hierarchy". The spec also says a mapped superclass "is not itself an entity". IOW, a mapped superclass should not be annotated with @Inheritance. SINGLE_TABLE is the default for inheritance hierarchies, so simply removing @Inheritance(strategy = InheritanceType.SINGLE_TABLE) from AbstractLogEventWrapperEntity should fix that.