[hibernate-issues] [Hibernate-JIRA] Commented: (EJB-456) Implement JPA 2.0 metamodel APIs

[ http://opensource.atlassian.com/projects/hibernate/browse/EJB-456?page=co... ] Steve Ebersole commented on EJB-456: ------------------------------------ 1) I don't understand what "is mapped ..." means. AFAIK, you mean that you interpret that as many-to-many in the annotation binder??? Obviously, if you tell core that something is a many-to-many, it treats it as a many-to-many :) javax.persistence.ManyToMany is the proper corollary to <many-to-many/>. In my limited knowledge, it looks like @OneToMany @JoinTable would map more naturally to: <join ...> <[collection type] ...> ... <one-to-many .../> </[collection type] ...> </join> which is not currently supported by core (collections within a <join/>). But, if that is a construct that needs to be supported then it should have been and should be accounted for in the hibernate metamodel properly. 3) It was in the PFD. Looks like it is since removed and its members pulled up into Attribute (Attribute had extended Member). But the same concern remains; now from Attribute: /** * Return the java.lang.reflect.Member for the represented * attribute. * * @return corresponding java.lang.reflect.Member */ java.lang.reflect.Member getJavaMember(); Ok, great... java.lang.reflect.Member can be either a Field or a Method. So what are we returning when? I mean the logical answer seems to be based on the access. For field access return the Field. But what about method access? The getter? -- 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