Steve Ebersole ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYTEyYmQ2NGVk... ) / Sub-task ( https://hibernate.atlassian.net/browse/HHH-16012?atlOrigin=eyJpIjoiYTEyYm... ) HHH-16012 ( https://hibernate.atlassian.net/browse/HHH-16012?atlOrigin=eyJpIjoiYTEyYm... ) Develop an abstraction for Class, Method, Field ( https://hibernate.atlassian.net/browse/HHH-16012?atlOrigin=eyJpIjoiYTEyYm... ) Change By: Steve Ebersole ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) When processing a domain model to build the metamodels, Hibernate needs to be careful about loading Class references. This is part of the purpose of HCANN. However, HCANN has a huge drawback in that it This is not able to handle models which do not have a 1-1 correspondence between {{ManagedType}} and {{Class}} ( critical for supporting both dynamic models and ` “ entity-name ” mappings ). Thus far To date , Hibernate has only supported either of those features through in its proprietary {{hbm.xml}} mappings format. Since However, since {{hbm.xml}} has been deprecated and its “extensions” moved into a defined in Hibernate’s {{orm.xml}} (JPA) extension XSD, we need to start supporting those these features in what is today called “annotation processing binding ”. This is part of what the [proposal|https://github.com/hibernate/hibernate-orm/discussions/5998] terms the “source model” (the other part being [https://hibernate.atlassian.net/browse/HHH-15996|https://hibernate.atlass...] ). ( https://hibernate.atlassian.net/browse/HHH-16012#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16012#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=Em... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100214- sha1:c40e72a )