Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Register generated classes for reflection #6

Open
angrymango opened this issue Feb 15, 2021 · 4 comments · May be fixed by #77
Open

Register generated classes for reflection #6

angrymango opened this issue Feb 15, 2021 · 4 comments · May be fixed by #77

Comments

@angrymango
Copy link
Contributor

When the jOOQ code generator is used the the generated classes should be registered for reflection so that they can be used in native binaries.

@laurentperez
Copy link

hello. any plans ? ;)

@angrymango
Copy link
Contributor Author

Yes but getting the time to do it is challenging at the moment

@ThoSap
Copy link

ThoSap commented Jan 27, 2022

Hi,
I managed to get jOOQ 3.16.3 Java 17 (Pro) running with GraalVM 21.3.0 Java 17 CE (Java Version 17.0.1+12-jvmci-21.3-b05) using DefaultRecordMapperSubstitutions.java and the following "workaround" to register the generated jOOQ classes for reflection using a custom Gradle task that runs every time before the compileJava Gradle task is executed:
https://stackoverflow.com/questions/65798326/quarkus-native-reflection-configuration-for-whole-package/70870930#70870930

@apatrida
Copy link

How would the extension know what classes you generated for your schema? Wouldn't it be better to change the schema generation strategy to support marking for reflection?

@luneo7 luneo7 linked a pull request Jun 22, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants