[hibernate-issues] [Hibernate-JIRA] Commented: (METAGEN-37) MappedSuperclass with type parameters result in uncompilable metamodels

[ http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-37?page... ] Hardy Ferentschik commented on METAGEN-37: ------------------------------------------ Seems {{TypeUtils.extractClosestRealTypeAsString()}} is doing this wrong thing. Currently the generated AttachmentGroup_ is: {code} package org.hibernate.jpamodelgen.test.typedmappedsuperclass; import javax.persistence.metamodel.SetAttribute; import javax.persistence.metamodel.SingularAttribute; import javax.persistence.metamodel.StaticMetamodel; @StaticMetamodel(AttachmentGroup.class) public abstract class AttachmentGroup_ { public static volatile SingularAttribute<AttachmentGroup, Long> id; public static volatile SetAttribute<AttachmentGroup, Post<UserRoleType>> posts; } {code} It really should be: {code} package org.hibernate.jpamodelgen.test.typedmappedsuperclass; import javax.persistence.metamodel.SetAttribute; import javax.persistence.metamodel.SingularAttribute; import javax.persistence.metamodel.StaticMetamodel; @StaticMetamodel(AttachmentGroup.class) public abstract class AttachmentGroup_ { public static volatile SingularAttribute<AttachmentGroup, Long> id; public static volatile SetAttribute<AttachmentGroup, AttachmentGroupPost> posts; } {code} Correct? WDYT? -- 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