-
Notifications
You must be signed in to change notification settings - Fork 40.2k
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
EntityTrackingRevisionListener is not spring managed since 3.1.1 #36511
Comments
This may be related to spring-projects/spring-framework#30545, https://hibernate.atlassian.net/browse/HHH-16069, and https://hibernate.atlassian.net/browse/HHH-16935 but it's hard to be certain without a reproducer. If you would like us to spend some more time investigating, please spend some time providing a complete yet minimal sample that reproduces the problem. You can share it with us by pushing it to a separate repository on GitHub or by zipping it up and attaching it to this issue. |
Projects here. They are failing on DDL but it still reproduces the error. |
Seems like the same issue as the one I reported. Note that there's a workaround of providing the spring property Once hibernate applies their fix you'll have to set the property to Edit: The below should demonstrate that it's the same issue, causing the same error without using the |
Thanks, @1dEraNCeSIv0, that confirms my suspicion. This will have to be addressed in Hibernate. |
Thank you for clarifying |
We are using hibernate envers with custom revision table created by EntityTrackingRevisionListener.
Usage:
In spring boot 3.1.0, somehow dependency resolution works and inject spring managed bean
CoreSecurityService
so it is not null.Since 3.1.1 it does not work and our
coreSecurityService
is null.It seems to me that we have took advantage of some bug because I cannot find how spring could inject beans into hibernate managed objects.
The text was updated successfully, but these errors were encountered: