-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update documentation for handling proxies in native-mode #45004
Update documentation for handling proxies in native-mode #45004
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I spotted a small typo.
I'm not sure I'm completely sold about merging the two sections given how this document has been built (and given these are two very different scopes). But happy to be proven wrong if you have a strong opinion about it :)
@@ -650,11 +644,15 @@ public class S3Processor { | |||
} | |||
---- | |||
|
|||
Using such a construct means that a `-H:DynamicProxyConfigurationResources` option will automatically be added to the `native-image` command line. | |||
This will allow Quarkus to generate the necessary configurtion for handling the proxy class. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will allow Quarkus to generate the necessary configurtion for handling the proxy class. | |
This will allow Quarkus to generate the necessary configuration for handling the proxy class. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice catch! You have eagle eyes :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🦅 fixed
Using such a construct means that a `-H:DynamicProxyConfigurationResources` option will automatically be added to the `native-image` command line. | ||
This will allow Quarkus to generate the necessary configurtion for handling the proxy class. | ||
Alternatively, you may create a `proxy-config.json` file under the `src/main/resources/META-INF/native-image/<group-id>/<artifact-id>` folder. | ||
For more information about the format of this file, see the link:https://www.graalvm.org/{graalvm-docs-version}/reference-manual/native-image/metadata/#dynamic-proxy-metadata-in-json[Dynamic Proxy Metadata in JSON] documentation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FWIW, you don't need the link:
when it's a URL starting with https?://
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just followed the existing pattern (it's easier than visiting the docs :) )
Removed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh yeah, it was more for the future, no worries.
* Merge "Managing Proxy Classes" sections. * Remove outdated mention to `-H:DynamicProxyConfigurationResources` Quarkus no longer uses `-H:DynamicProxyConfigurationResources` for dynamic proxies. Instead it generates the corresponding necessary metadata in `META-INF/native-image/proxy-config.json`
733b819
to
c09ade9
Compare
🙈 The PR is closed and the preview is expired. |
Status for workflow
|
Oh, I never commented on that but it looks like you went ahead with it anyway. |
Yeah, I understand the thing about duplication but in this case, things are a bit rather different between extensions and apps. If you can add a pointer, that would be perfect. |
Follow up to quarkusio#45004 (cherry picked from commit 036cc7f)
-H:DynamicProxyConfigurationResources
Quarkus no longer uses
-H:DynamicProxyConfigurationResources
fordynamic proxies. Instead it generates the corresponding necessary
metadata in
META-INF/native-image/proxy-config.json