[GR-47365] Integrate proxy registration to the reflection config #8822
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.
This PR includes the registration of proxy classes for runtime instantiation into the reflection configuration. This allows the registration of reflection queries on proxy classes, which was not possible until now.
The existing handling of proxy configuration files is still here to handle existing files, but the agent is modified to use the new behavior.
The new format to specify proxy classes is the following:
Here's a summary of the main changes:
BreakpointInterceptor
) is modified to consistently handle proxy classes, instead of the case-by-case approach used until now. Proxies are encoded as an array of interfaces in the trace files;ProxyConfigurationTypeDescriptor
enables handling of proxy classes in configuration code;ConfigurationTypeDescriptor
from parsing onwards, notably inConfigurationType
;ReflectionRegistry
now takes aProxyRegistry
to register proxy classes.