Repository navigation
Fix audit repository proxy loading in packaged applications - #55
Merged
Merged
Conversation
ancongui
enabled auto-merge
November 3, 2026 01:01
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
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.
Audit repository proxies could fail with
ProxyBuilder.ensureVisiblewhen created on a request thread whose context class loader cannot see interfaces inside a Spring Boot nested JAR. This prevented real audited Accounts reservation operations from completing.Set the bean class loader on each of the two internal
R2dbcRepositoryFactoryinstances to the loader of its declared repository interface. This preserves Spring Data repositories, transaction ownership and audit checks, and does not mutate the caller thread context or open a connection during construction.Validation on current main
48d27323e3862202950f5fcf5a13872664ff528c: both new regressions fail before the correction; all 172 current r2dbc module cases pass after it. A separate test-only nested-executable composition loads both actual candidate audit proxies with the system context loader and succeeds without changing it. Root independently checked the exact three-path candidate tree and all 20 retained JUnit reports.The equivalent fix on the released-source baseline was separately exercised by real Accounts packaged HTTP and PostgreSQL persistence tests. That evidence does not establish current-main consumer adoption or a published release. No version bump, artifact installation or replacement of an existing release is included.