|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
The entity-name attribute of Hibernate core is useful (among other reasons) for referencing mapped entity types with interface names and not class names. This way you can build libraries that expose to the users the interface and not the actual implementation which can vary according to needs and reside in another library.
Therefore I strongly vote in favor of supporting entity-names in Hibernate Search by simply adding an getEntityName() function in org.hibernate.annotations.common.reflection.XClass. Then all calls to org.hibernate.search.cfg.spi.SearchConfiguration.getClassMapping(String name) (I have counted 2 but there could be more) can be done using xClass.getEntityName() and not xClass.getName().
I hope this helps.