You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains 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
Open and Fix NativeTest by Spring Framework under GraalVM CE.
Other information:
DynamicRoutingDataSource has design flaws. This class attempts to inject a List<DynamicDataSourceProvider> Spring Bean into a non-container environment, which causes the Spring Framework to deliberately take over this class and set a NoArgConstructor for this class with an unaligned parameter list.
Similarly, Alibaba Druid's Spring Boot Starter has a similar problem with Spring Bean introspection failures, resulting in the Spring Framework's improper initialization of beans.
DynamicRoutingDataSource has design flaws. This class attempts to inject a List<DynamicDataSourceProvider> Spring Bean into a non-container environment, which causes the Spring Framework to deliberately take over this class and set a NoArgConstructor for this class with an unaligned parameter list.
Similarly, Alibaba Druid's Spring Boot Starter has a similar problem with Spring Bean introspection failures, resulting in the Spring Framework's improper initialization of beans.
I'll discuss how to manage GraalVM Reachability Metadata and convert Standard Metadata to Conditional Metadata in a new issue. Now the downstream still needs to add some of the contents of the JSON file itself. But the core problem has been solved, because nativeTest has already run through.
From this point of view, apart from the fact that SPEL cannot be used, we can claim that dynamic-datasource should not conflict with GraalVM Native Image.
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.
What kind of change does this PR introduce? (check at least one)
The description of the PR:
Other information:
DynamicRoutingDataSourcehas design flaws. This class attempts to inject aList<DynamicDataSourceProvider>Spring Bean into a non-container environment, which causes the Spring Framework to deliberately take over this class and set a NoArgConstructor for this class with an unaligned parameter list.As a fix, I added a AllArgsConstructor for
DynamicRoutingDataSourceto avoid https://github.com/baomidou/dynamic-datasource/actions/runs/6080472779/job/16494489274?pr=560 display, injectedList<DynamicDataSourceProvider>is null.Similarly, Alibaba Druid's Spring Boot Starter has a similar problem with Spring Bean introspection failures, resulting in the Spring Framework's improper initialization of beans.