Repository navigation
Use JPAMetaModel classes
#37827
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Currently in Keycloak criteria queries are using hardcoded string attributes and named query. Instead we can replace it with classes generated by hibernate processor. Using this we will have compile type check for attributes and named queries.
Just wanted to check whether there are any reasons for not using it before creating un-necessary issues.
I can raise a PR if we agree on using metamodel processor.
All reactions