Fix tenant-aware connection factory lookup in HeaderBasedMultiTenantConnectionFactory - #686
Open
ralfkuehnel wants to merge 2 commits into
Open
Conversation
Member
|
Hey @ralfkuehnel, Can you add test case using Ecotone Lite, which would fail without this fix? (to avoid regression bugs in future) |
Member
|
Do you need any help from my side @ralfkuehnel ? |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Why is this change proposed?
Pass the resolved tenant to
getConnectionFactory()so the connection factory is looked up using the correct tenant context instead of relying solely on the current execution context.Description of Changes
Passing the tenant through ensures consistent tenant resolution and correct connection factory selection.
Pull Request Contribution Terms