Steve Ebersole (
https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%...
) *updated* an issue
Hibernate ORM (
https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMWZjODlkZjdh...
) / Improvement (
https://hibernate.atlassian.net/browse/HHH-16633?atlOrigin=eyJpIjoiMWZjOD...
) HHH-16633 (
https://hibernate.atlassian.net/browse/HHH-16633?atlOrigin=eyJpIjoiMWZjOD...
) Render "repository" methods into generated metamodel (
https://hibernate.atlassian.net/browse/HHH-16633?atlOrigin=eyJpIjoiMWZjOD...
)
Change By: Steve Ebersole (
https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%...
)
For simple named queries, generate “repository” methods.
E.g.
{code:java}@NamedQuery(
name = "persons_by_city",
query = "from Person where city = :theCity"
...
)
@Entity
class Person {
...
@Basic String city;
}{code}
leads to
{code:java}@Generated
class Person_ {
...
public static List<Person> getPersonsByCity(String city, Session session) { ... }
}{code}
An alternative would be to instead generate a distinct repository class which might be
better given that:
# Hibernate named-queries can be defined at the package level
# JPA static metamodel generation effective has to be done from an annotation processor;
I’m not sure how feasible it is to do this from an annotation processor. We need to be
able to parse the query (into SQM most likely) for semantic information. Again, not sure
how feasible it is to do this from an annotation processor.
(
https://hibernate.atlassian.net/browse/HHH-16633#add-comment?atlOrigin=ey...
) Add Comment (
https://hibernate.atlassian.net/browse/HHH-16633#add-comment?atlOrigin=ey...
)
Get Jira notifications on your phone! Download the Jira Cloud app for Android (
https://play.google.com/store/apps/details?id=com.atlassian.android.jira....
) or iOS (
https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=Em...
) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100225- sha1:2b972a1 )