Fix #13425 Hibernate ORM and Hibernate Reactive cannot be used in the same application#44473

Open

lucamolteni wants to merge 29 commits intoquarkusio:mainfrom lucamolteni:13425-ter

+1,235-220

Commits on Feb 27, 2025

Hibernate ORM and Hibernate Reactive cannot be used in the same application quarkusio#13425
lucamolteni
committed
Do not assume a blockng pu is needed, if it's reactive but we don't have a JDBC data source we don't generate the blocking pU
lucamolteni
committed
Fix a few test injecting the session factory with -reactive just for metadata
lucamolteni
committed
Removed isReactive fields as they're in QuarkusPersistenceUnitDescriptor
lucamolteni
committed
Removed useless field from test
lucamolteni
committed
quarkus.datasource.reactive=true removed
lucamolteni
committed
Moved deployments dependencies
lucamolteni
committed
Removed auth details
lucamolteni
committed
Removed ReactivePersistenceUnit annotation, generated the Mutiny.SessionFactory bean in the extension itself
lucamolteni
committed
Fixed ConfigActiveFalseAndEntityTest, property disable the reactive PU as well
lucamolteni
committed
No need for ImpliedBlockingPersistenceUnitTypeBuildItem impliedBlockingPersistenceUnitType in HibernateReactiveCdiProcessor
lucamolteni
committed
Take included entities from default persistence unit (orm) name as well
lucamolteni
committed
Unwrap the proxy because it doesn't directly implement that interface
lucamolteni
committed
Redisabled tests by default
lucamolteni
committed
Revert "Fixed ConfigActiveFalseAndEntityTest, property disable the reactive PU as well"
lucamolteni
committed
formatting
lucamolteni
committed
ORMReactiveCompatbilityUnitTest
lucamolteni
committed
Fix one UnsupportedPropertiesTest
lucamolteni
committed
Use DataSourcesReactiveBuildTimeConfig to understand if the default data source supports reactive to avoid failing while using reactive and blocking together
lucamolteni
committed
Formatting
lucamolteni
committed
Renabled "disabled" PU in the only reactive case
lucamolteni
committed
Changed if avoiding > 1 (prevents multiple beans to be instantiated)
lucamolteni
committed
Formatting
lucamolteni
committed
Better handling of multiple sessionfactories (with added test to ORM suite)
lucamolteni
committed
Provide a ClassNames class + test in reactive as well
lucamolteni
committed
Removed comment
lucamolteni
committed
Reverted NoJTATest
lucamolteni
committed
Skip integration test in default profile
lucamolteni
committed
formatting
lucamolteni
committed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Fix #13425 Hibernate ORM and Hibernate Reactive cannot be used in the same application#44473

Commits on Feb 27, 2025

Hibernate ORM and Hibernate Reactive cannot be used in the same application quarkusio#13425

Do not assume a blockng pu is needed, if it's reactive but we don't have a JDBC data source we don't generate the blocking pU

Fix a few test injecting the session factory with -reactive just for metadata

Removed isReactive fields as they're in QuarkusPersistenceUnitDescriptor

Removed useless field from test

quarkus.datasource.reactive=true removed

Moved deployments dependencies

Removed auth details

Removed ReactivePersistenceUnit annotation, generated the Mutiny.SessionFactory bean in the extension itself

Fixed ConfigActiveFalseAndEntityTest, property disable the reactive PU as well

No need for ImpliedBlockingPersistenceUnitTypeBuildItem impliedBlockingPersistenceUnitType in HibernateReactiveCdiProcessor

Take included entities from default persistence unit (orm) name as well

Unwrap the proxy because it doesn't directly implement that interface

Redisabled tests by default

Revert "Fixed ConfigActiveFalseAndEntityTest, property disable the reactive PU as well"

formatting

ORMReactiveCompatbilityUnitTest

Fix one UnsupportedPropertiesTest

Use DataSourcesReactiveBuildTimeConfig to understand if the default data source supports reactive to avoid failing while using reactive and blocking together

Formatting

Renabled "disabled" PU in the only reactive case

Changed if avoiding > 1 (prevents multiple beans to be instantiated)

Formatting

Better handling of multiple sessionfactories (with added test to ORM suite)

Provide a ClassNames class + test in reactive as well

Removed comment

Reverted NoJTATest

Skip integration test in default profile

formatting