Zheng Feng

The `hibernate-orm-panache` is failing in native build and I will investigate.

@mmusgrov these three classes **CAN NOT** be added to initlize at runtime currently. ```java runtimeInit.produce(new RuntimeInitializedClassBuildItem(UserTransactionImple.class.getName())); runtimeInit.produce(new RuntimeInitializedClassBuildItem(TransactionManagerImple.class.getName())); runtimeInit.produce(new RuntimeInitializedClassBuildItem(BaseTransaction.class.getName())); ``` It looks like `hibernate-orm-panache` has something to use `TransactionManager`...

@gastaldi I think the reflection increase is expected.

Thanks @gsmet - I seperate revert commit in - https://github.com/quarkusio/quarkus/pull/40334

For fixing #39283 , it is not needed. But if we still want to support system properties in the native mode, it is necessary.

Thanks @turing85 for the reproducer! I'm sorry that I have to say these codes were working before but not **right**. In your case, if you want to do the `db...

> can you clarify that last question ? Yeah, in previous version, if it involves multi non-XA datasources in a transaction, Narayana Transaction Manager **CAN NOT** guarantees that **DO THEM...

Thanks @p91paul and yeah, I think we can improve to support multiple files. Are you interesting to contribute?

@jamesnetherton `quarkus-tika` upgrade to `2.0.0.CR1` which depends on `tika` 2.7.0 now. So I think we could revert this workaround and close this issue?

I think so. Take a look at - https://github.com/quarkiverse/quarkus-dapr/pull/133 @skyao can you check it from dapr side? I only find https://github.com/dapr/java-sdk/blob/master/sdk/pom.xml#L58-L62