issue-50138-hibernate-orm-named-qualifier #50453
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks for your pull request! Your pull request does not follow our editorial rules. Could you have a look?
This message is automatically generated by a bot. |
|
/cc @gsmet (hibernate-orm) |
Consistently apply @nAmed and @PersistenceUnit qualifiers to Hibernate ORM beans Fixes quarkusio#50138 Previously, the @nAmed and @PersistenceUnit qualifiers were added conditionally to Hibernate ORM beans. This change ensures that both qualifiers are always applied for every persistence unit, aligning the behavior with Hibernate Search and improving consistency and CDI injection reliability across the codebase. Tests are updated to confirm that beans are correctly qualified and injected for each persistence unit.
Aryant-Tripathi
force-pushed
the
issue-50138-hibernate-orm-named-qualifier
branch
from
e167e57 to
e80fea1
Compare
yrodiere
reviewed
Oct 8, 2025
...kus/hibernate/orm/multiplepersistenceunits/MultiplePersistenceUnitsCdiEntityManagerTest.java
Show resolved
Hide resolved
…te ORM beans - Previously, the @ Named and @PersistenceUnit qualifiers were added conditionally to Hibernate ORM beans. This change ensures that both qualifiers are always applied for every persistence unit, aligning the behavior with Hibernate Search and improving consistency and CDI injection reliability across the codebase. - Tests are updated to confirm that beans are correctly qualified and injected for each persistence unit. - Fixes quarkusio#50138
yrodiere
approved these changes
Oct 9, 2025
|
LGTM, thank you. Let's see if CI agrees. |
yrodiere
added
the
triage/waiting-for-ci
Status for workflow
|
quarkus-bot
bot
added
kind/enhancement
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Consistently apply @ Named and @PersistenceUnit qualifiers to Hibernate ORM beans
Fixes #50138
Previously, the @ Named and @PersistenceUnit qualifiers were added conditionally to Hibernate ORM beans. This change ensures that both qualifiers are always applied for every persistence unit, aligning the behavior with Hibernate Search and improving consistency and CDI injection reliability across the codebase.
Tests are updated to confirm that beans are correctly qualified and injected for each persistence unit.