-
Notifications
You must be signed in to change notification settings - Fork 51
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
Can not run native with quarkus-jaxp and quarkus-jaxb #359
Comments
There's probably something else at play here because the error doesn't seem like it'd be something impacted by XML parsing… |
Actually, strike that… Do you have JAXP/JAXB annotations on your custom resource? |
Just to be sure: the same code works in JVM mode? Also, is there a way to replicate the issue? |
@metacosm I have just made some attempts. If I ignore these errors, native service returns to its normal state after continuously reporting errors for a period of time. |
The reason why I introduced jaxb and jaxp is that I found some errors like the following errors when parsing xml. Therefore, I imported these two packages to solve the instantiation of related classes.
I mainly parse xml files and xml text, but I haven't used annotations yet. |
I will do more tests to confirm the core of the problem. Please wait a little longer. |
@metacosm At present, I still can't debug the native mode, so I don't know which object is not initialized. Can you continue to track this problem? |
The problem that occurs is that most likely your resource is not being properly deserialised due to some conflict between Jackson (which is heavily used by the fabric8 client) and JAXB/JAXP… so in the code above, the NPE most likely occurs because Now the question is why the resource cannot properly be deserialised? Without being able to replicate the issue, it's difficult to tell. Is running natively a requirement? It's important to note that for the operator use case, native compilation is typically less interesting than for micro services. Indeed, operators behave similarly to traditional server applications for which the JVM is particularly well suited so the benefits of native compilation are smaller for operators. |
@metacosm |
I have some requirements for parsing xml, so I import
quarkus-jaxp
andquarkus-jaxb
. However, I found that after native compiled and started operator, the operator would have the following errors.Here is my jaxb and jaxp import packages, I use quarkus 2.9.2 and oeprator-sdk 4.0.0.RC.
The text was updated successfully, but these errors were encountered: