Vertx Context is broken when calling HR after the KC client

[acasanova99]

For some reason the context of quarkus is not propagated correctly among the application and the client.

After calling this client, if we access a state-full context method, as the HR#withSession(), it will cause the following failure:

ERROR while persisting the user The current operation requires a safe (isolated) Vert.x sub-context, but the current context hasn't been flagged as such. You can still use Hibernate Reactive, you just need to avoid using the methods which implicitly require accessing the stateful context, such as MutinySessionFactory#withTransaction and #withSession.

Possible causes:

• Version between the main app and this client are different. (Will be solved in the next update of the client)
• This client is a dependency but not a quarkus extension. (We will covert this client into a quarkus extension in a near future)