Adapt native support for Hibernate 6.3.0 bytecode provider changes #31051
Assignees
Labels
in: data
Issues in data modules (jdbc, orm, oxm, tx)
theme: aot
An issue related to Ahead-of-time processing
type: enhancement
A general enhancement
Milestone
Comments
sdeleuze
added
in: data
|
Related: #30521 (comment) |
@Eng-Fouad I did some related tests and found it seems to not fail in practice due to inlining of the |
Here is a reproducer: https://github.com/Eng-Fouad/spring-boot-native-3.1.3-with-hibernate-6.3.0 |
|
Thanks for the reproducer, so far Spring Boot 3.1 and related Spring Framework version are not supporting Hibernate 6.3, so that's expected. For next Spring Boot 3.2 milestone or RC, it should work with the changes implemented in #29549 and when using Hibernate |
|
Setting Stacktrace: |
|
@vladimirfx What is your use case for setting explicitly |
We use JVM. Conceptually I against proxies especially when build time weaving already done. We use Kotlin mostly and I won't open my classes. Up to 6.3 all works as expected. |
|
Spring uses a workaround (native substitution), Quarkus uses a workaround (native substitution + pregenerated proxies). I can't understand why a valid configuration is 100% nonfunctional and no issues are created... |
|
I don't challenge the relevancy of your ask, I was just curious of your use case. I have created the related https://hibernate.atlassian.net/browse/HHH-17568 issue since that should indeed be fixed on Hibernate side. |
sdeleuze
added a commit
to sdeleuze/spring-framework
that referenced
this issue
Dec 14, 2023
Thank you so much! |
|
@sdeleuze Do you have any insights outside of the information on the ticket https://hibernate.atlassian.net/browse/HHH-17568? We're running into this issue as well. Also 3.1.3, since 3.2.1 and 3.2.2 seem to be broken for native-image due to spring-projects/spring-security#14362 |
|
@StevenPG Nope, but this issue is expected to be fixed by the the substitution, and an upcoming fix seems planned for Hibernate 6.4.4 as mentioned in the issue. The Spring security bug will be fixed in Boot 3.3.3 as mentioned in this comment. So there should be no issue with Boot + Security latest snapshots. If you see something broken, please create an issue with minimal repro. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The native support for Hibernate should be refined in order to be compatible with those changes related to the bytecode provider management expected to be part of the upcoming Hibernate
6.3.0.Finalrelease.We should also retain compatibility with previous versions down to Hibernate
5.6.x.We should test such refined Hibernate support using our AOT smoke tests using Hibernate
6.3.0.CR1(or a more recent version available).The text was updated successfully, but these errors were encountered: