-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
Warnings Question #254
Comments
Are you seeing that with this project in 3.0.0. Beta1 ?? I have not tried it in a few weeks but I don't remember seeing these |
You can add |
Yes. I just pulled the repo fresh and it is set to 3.0.0.Beta1.
Would the @RegisterForRelefction have to be added upstream in the
primefaces and omnifaces project?
Would those projects consider adding that annotation as too
"quarkus" specific?
Or, is there a config file - xml descriptor or similar - we could feed to
graalvm to register all of these classes?
Or, maybe the pattern of *_ClientProxy?
…On Wed, Mar 29, 2023 at 10:49 AM Melloware ***@***.***> wrote:
You can add @RegisterForRelefction on any class you want registered
—
Reply to this email directly, view it on GitHub
<#254 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABUGXHS63VZ3N2275KOIK7LW6RR2VANCNFSM6AAAAAAWMEN35U>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
if you can give me an example class that is not registered I need to add them to the PF Extension so they get registered. |
I've grepped out the warnings. But, now I'm wondering if there is something else going on. There are classes indicated that seem odd like those in java.lang and java .util
Some from the jakarta project which struck me as interesting...
|
Should have snipped off the ClientProxy parts
|
That is really weird the Faces stuff is all already registered by the MyFaces extension and all the PF stuff is already registered. As for showcase that is also wrong as I already have this on the
So I think something is wrong. this is all working with 2.16.4 so something tells me Beta1 might have an issue with it |
I will give everything a try and let you know. |
Interesting I just pulled the latest code and on Windows I am getting this... This was all working with a previous 3.0.0.Alpha.
|
Opened: quarkusio/quarkus#32272 |
OK @gesker i just built the latest Quarkus Faces using my Linux machine instead of Windows and the native image built fine and worked out of the box. So not sure exactly all the issues you are having? |
I'm good to go on CR1 |
OK I just updated PF and OF extensions to CR1 and deployed to Maven Central. |
GraalVM is issuing a lot of reflection related warnings
Warning: Could not resolve xyz.somepackage_ClientProxy for reflection configuration. Reason: java.lang.ClassNotFoundException: xyz.somepackage_ClientProxy_ClientProxy.
is there a clean way to have GraalVM work around these classes without warnings? Or, really, handle these better?
I'm guessing "--initialize-at-run-time" would NOT be the way to go as I could see one quickly hitting a point where there would just be too many command line parameters.
The text was updated successfully, but these errors were encountered: