[hibernate-issues] [Hibernate-JIRA] Commented: (ANN-528) avoid auto import of superclasses to avoid inheritance mapping
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-528?page=co...
]
Emmanuel Bernard commented on ANN-528:
--------------------------------------
If your framework closed the entity source, there should be a reason.
I gues the standard way to do that would be to override the mappings completly using
metadata-complete=true, but it creates duplication.
I don't exactly understand what the annotation is supposed to do, can you elaborate?
avoid auto import of superclasses to avoid inheritance mapping
--------------------------------------------------------------
Key: ANN-528
URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-528
Project: Hibernate Annotations
Type: New Feature
Components: binder
Reporter: Armin Haaf
It is not possible to avoid inheritance mapping if the superclass of a entity is also a
entity.
Background: A framework provides a basic mapping of a entity, but I want to extend that.
With annotations it is not possible to just map my extended version and have the
superclass behave like a MappedSuperclass. This behaviour is acceptable but it is not
possible to override a the id generation.
So it might be better to have a new annotation (e.g. @RootEntity(mapSuperclass=true)) to
avoid auto import of the entity superclass. With that approach it would be easier to
create modules and frameworks
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira