[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-3842) Additional annotations support for "Generate Hibernate/JPA annotations"

[Max Rydahl Andersen (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-3842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12453752#action_12453752 ] 

Max Rydahl Andersen commented on JBIDE-3842:
--------------------------------------------

Ok, but you can't just look at the hierarchy of the class to know if mapping it as a hierarchy is correct
and just mapping it blindly for all would result in very non-performant mappings.

So if we do this we should at least have it disabled by default and maybe have it as a checkbox on
the first page saying: "Add @MappedSuperclass for base classes" which if checked would do it.
But even then we have to be careful since @MappedSuperclass would have no corresponding table.
A good best guess is that you only add it to abstract super classes to avoid problems.





> Additional annotations support for "Generate Hibernate/JPA annotations"
> -----------------------------------------------------------------------
>
>                 Key: JBIDE-3842
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-3842
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: Hibernate
>    Affects Versions: 3.0.0.CR2
>            Reporter: Vitali Yemialyanchyk
>            Assignee: Vitali Yemialyanchyk
>            Priority: Minor
>
> currently I see the sence add @MappedSuperclass annotation for base class instead of or together with @Entity annotation;
> in case when the class has offsprings - there is a big sence to have @MappedSuperclass annotation by default.
> Some other ideas?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira