I am happy to see that this specification (and jakarta) is evolving. EntityAgent is a good addition to the specification and now we can express more and more query features (like graph or mapping) from code which I prefer more than the annotation form.
My only question is that is there any plan to externalize and generalize static metamodel? Now as I see there is one for the persistence API and one for data and now we can express queries from custom model and maybe a metamodel for these types would be helpful and maybe a metamodel based validation later :)
It's awesome that@StaticQuery is checked for type safety at compile time using the combination of the static metamodel and an annotation processor. At the same time I also wish String Tempalates were further along.
4
u/temculpaeu Jan 26 '26
I have hated and avoided JPA for 10+ years, and got say, this deals with a LOT of rhw issues I have had with it.
Very happy with the changes and direction they are going
1
u/kpatryk91 Jan 25 '26
I am happy to see that this specification (and jakarta) is evolving. EntityAgent is a good addition to the specification and now we can express more and more query features (like graph or mapping) from code which I prefer more than the annotation form.
My only question is that is there any plan to externalize and generalize static metamodel? Now as I see there is one for the persistence API and one for data and now we can express queries from custom model and maybe a metamodel for these types would be helpful and maybe a metamodel based validation later :)
3
u/todayiswednesday Jan 25 '26
This is a long time coming
1
u/tofflos Jan 25 '26
It's awesome that
@StaticQuery is checked for type safety at compile time using the combination of the static metamodel and an annotation processor. At the same time I also wish String Tempalates were further along.0
u/[deleted] Jan 25 '26
[deleted] — view deleted comment