Bug Report

Summary

I receive a mapping exception after defining an inverse-side association on an abstract entity. A mapped superclass extends the abstract entity. A concrete entity extends the mapped superclass.

Current behavior

ClassMetadataFactory is currently throwing an exception if there is an inverse-side association on a mapped superclass.

This is correct, as stated in the documentation. However, I believe this limitation should be imposed only if the association is on the mapped superclass itself.

How to reproduce

• Define an abstract entity (A).
• Define a mapped superclass (B) extends A.
• Define a concrete entity (C) extends B.
• Define another entity (D) that has a many-to-one relationship with A.

I will follow-up with a failing test case.

Expected behavior

I think the above mapping should be valid since the association is not defined directly on the mapped superclass.