-
Notifications
You must be signed in to change notification settings - Fork 2
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
Class initialization and native executable issue #54
Comments
Hi. Due to some resourcing shortage lately we have not had time to look into the native compilation of a vaadin project. But due to the exception I would like to know if you are using SpringBoot and what version of tomcat are you using? |
Hi! I'm not using Spring Boot. I'm using Quarkus 2.5.2.
As you can see, it tells that the class What I see is that when creating the native executable, it starts initializing all of the |
As there is issues with Push on websockets you could try to exclude the flow-push dependency and see if that helps as the Atmosphere shouldn't be initalized. This would at least hopefully give some insight to what is happening |
I tried doing that (and explicitly adding
|
I fiddled with native compilation a while as well, but couldn't easily get flow-push/atmosphere to work. Getting rid of it completely works, but then, well, there is no server side push... Pushed out my example based on the base starter here: https://github.com/vaadin/base-starter-flow-quarkus/tree/native-image |
Created an enhancement issue about built-in hints for "native compilation hints": #72 |
BTW. I got quite a lot further with flow-push/atmosphere. Requesting runtime initialization for most atmosphere classes gets you forward, but I got frustrated at a point when got complaints about Thread usage. Didn't know anymore what to do with these, without starting to write a replacement/fork for atmosphere framework:
|
Hi, as you can read from the title, I'm having some issues when building a native executable.
The command that I'm using is the following:
export NODE_OPTIONS=--openssl-legacy-provider ./gradlew vaadinClean vaadinBuildFrontend build \ -Pvaadin.productionMode \ -Dquarkus.package.type=native
When executing that, several stacktraces appear saying that class initialization fails:
In order to avoid this, I added the following to the
application.properties
files:However, it doesn't seem to work. Those classes are still getting initialized.
Is there something I'm missing?
Quarkus version:
2.5.2.Final
.Vaadin version:
22.0.2
The text was updated successfully, but these errors were encountered: