Got this started. Wanted to keep track of a couple of points/todos.
* {{org.hibernate.annotations.NamedQuery}} seems completely superfluous, as its function could be achieved completely using {{javax.persistence.NamedQuery}} and query-hints . We should consider deprecating it.
* Same for {{org.hibernate.annotations.NamedNativeQuery}} / {{javax.persistence.NamedNativeQuery}}
* Legacy HBM allowed for callable attribute on {{<sql-query/>}}. Would prefer to not extend that into JPA's {{<named-native-query/>}}. The best option imo would be to map {{<sql-query ... callable="true"/>}} to {{<named-stored-procedure-query/>}}.
* Difference in JPA's and Hibernate's notion of "access" becomes problematic in certain usage. In cases where the JPA access was defined as an element there was no problem, I made the choice an {{xsd:choice}}. However sometimes JPA defines access as an XML attribute rather than an element. In such cases (iiuc) I'd have to make the Hibernate option an XML attribute as well in order to make it {{xsd:choice}}-able. I've tried to avoid making Hibernate extensions XML attributes. Any real reason for that?
* Inheritance seems like it will be a fun transformation :)
|
