-
Notifications
You must be signed in to change notification settings - Fork 116
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
hibernate-envers - UnsupportedOperationException #104
Comments
Can you include the stacktrace? I doubt hibernate would consider changing that for our use case. |
sure.
this is a bit related to grails/gorm-hibernate5#15 as that would at least allow to cleanly override the |
@zyro23 I don't think there is anything I can do on this end. I see the issue you linked is closed. Does that satisfy your requirement? |
linked issue has kind of a follow up as it fixed being able to register a custom service in envers but now the configuration of a custom mappingContextConfiguration is not working. ref. grails/gorm-hibernate5#17 anyway, thats the right place where this should be fixed. closing this one here. thanks! |
@zyro23 can you provide more information about your "ugly workaround"? Is this something that needs to be fixed in the "database-migration" plugin, or does it need to be fixed in the interface between Grails and Envers, for example, in an Envers plugin? I am experiencing the same problem using Grails 3.2.12 with GORM 6.1.6 and a version of the "grails-envers" plugin that has been ported to Grails 3. Thanks. |
I know that this issue was closed a long time ago, but i'm lost in getting dbm-gorm-diff running. Could you please give me some advice how to do it? Thanks. |
Same here, the plugin is broken for grails 4. |
Any update at all ? |
There is open issue #204 for this. |
dbm-3.0.0, grails-3.2.3, gorm-6.0.4, hibernate-5.0.11.
when using hibernate envers, all liquibase commands that involve two databases (e.g. dbm-gorm-diff - 1 gorm db, 1 real db) cause an
UnsupportedOperationException
here:https://github.com/hibernate/hibernate-orm/blob/5.0.11/hibernate-envers/src/main/java/org/hibernate/envers/boot/internal/EnversServiceImpl.java#L107
ugly workaround for now was to write a custom
ÈnversService
/ServiceContributor
/ServiceInitiator
that overrides the default hibernateEnversServiceImpl
.do we have any sane option to prevent that from happening or should we raise an upstream issue for hibernate-envers explaining the dbm diff use-case and request to remove that condition?
The text was updated successfully, but these errors were encountered: