Davide D'Alto

@gavinking Does this issue make sense? if yes, should we just move to jakarta and ignore the old ones?

There are two workaround for this: 1. Destroy the injected session object using arc: ``` Arc.container().instance(Mutiny.Session.class).destroy() ``` This way a new session will be recreated the next time. @mkouba Is...

I don't think we can close this issue, unless the session is actually recreated or replaced in case of error. If that's not the case, even if it might work...

It's possible to see the log via this test: https://github.com/hibernate/hibernate-validator/commit/b762667d4da175e16f1ffd5151921d0fc51a772d

Thanks @marko-bekhta, I will update the pr

I've tried the following test: ```java @Test public void testExceptionPropagation(VertxTestContext context) { test( context, getMutinySessionFactory() .withTransaction( session -> { int loop = 5000; Uni uni = Uni.createFrom().voidItem(); for ( int...

> should we expose our trampoline to users, or I think we should do it. We need to have a version for Mutiny and one for Stage (at least the...

[I think it's fair to say that StatementInspector doesn't work with Hibernate Reactive currently](https://github.com/quarkusio/quarkus/discussions/44308). As a workaround, this should work: You could create a wrapper around `ReactiveConnection` and intercepts all...

I updated the test case to the latest Quarkus here: https://github.com/DavideD/quarkus_27640/commit/1112d1c766ca58a4c41154f9311aba9e217a2f8f and I created a test with only Hibernate ORM (without Quarkus and Bytecode enhancements) here: https://github.com/DavideD/hibernate-test-case-templates/commit/a629441b60da1769172cbd72608d8a58f5ac6369 The test with...

I gave this issue another look and I don't know why we ignored @saiello [comment](https://github.com/saiello) containing the correct solution (sorry): ```java @OneToMany(mappedBy = "dependency", cascade = CascadeType.PERSIST) List requiredBy; ```...