[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-527?page=co... ] Armin Haaf commented on ANN-527: -------------------------------- We use interfaces to exchange the implementation without using inheritance mapping. You are right if you say it is not needed, it does the job without interfaces, but you loose the possibilty to avoid inheritance mapping if not needed. We also use interfaces to hide the setters! -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-527?page=co... ] Armin Haaf commented on ANN-527: -------------------------------- The interface is to hide them, not to make them unusable! If someone wants to exchange the implementation of an entity. -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-527?page=co... ] Börcsök József commented on ANN-527: ------------------------------------ I have a similar usecase: my domain model contains events and members. Events can be Camp or Conference (so event is an abstract entity, Camp and Conference contains specific properties too) Members have attributes like name, email, ... and CampMember and ConferenceMember also have specific properties. So my entity classes should be (using generics): event entities: Event, Camp extends Event, Conference extends Event member entities Member<T extends Event> (0..*) ---------<> (1..1) T CampMember extends Member<Camp> ConferenceMember extends Member<Conference> on deploy I've got the following exception: Property Member.event has an unbound type and no explicit target entity. Resolve this Generic usage issue or set an explicit target attribute (eg @OneToMany(target=) or use an explicit @Type @OneToMany annotation has no target but targetEntity property. I've tried the targetEntity property and the @Type annotation but neither has worked :( -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-527?page=co... ] Celso Gomes Barreto Jr commented on ANN-527: -------------------------------------------- In hbm.xml files you can specify the target entity name in a relationship. I don't know why shouldn't you be able to do this using annotations. I have a class on my application which I reuse as several entities, mapping it with different entity names stored in different tables. I'm still looking for a solution to do the relationship mappings using annotations. My team is skilled at the use of annotations and when they have to do the mapping using hbm.xml files, they find it very difficult. -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-527?page=co... ] IK commented on ANN-527: ------------------------ Hi, we need this feature to. In our case, the application is made of different modules with domain-logic. Each module has an interface and implemententation package. The public part of the domain-object is in die interface package. The compile-time dependencies are configured that modules can only depend on interfaces of other modules. Therefore module A has only access to the interface definitions on module B. If a Domain-Object in module A has a relationship to a Domain-Object in module B, the reference to the Domain-Object in module B cannot be a Domain Implementation-Class in our case. Therefore, with the "target-entity" annotation, we get a compile-error in module A. Solution is actually pretty easy. Patch in persistence-api-*.jar the Files: OnetoOne, OneToMany, ManyToOne and ManyToMany to Support "EntityTargetName" (as String) Annotation. And patch in hibernate-annotations-*.jar the class: org.hibernate/annotation/cfg/AnnotationBinder, in case TargetEntity is void, to use the TargetEntityName Annotation (and load the class with class.forName(...)). Would be nice to the something like that in the main development branch. -- 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