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
Jakarta - EE 10 - Weird Jackson serialization issue in REST Data Panache #28016
Comments
/cc @FroMage, @geoand, @loicmathieu |
cc @Sgitario |
I could find the root cause of this issue. From Jackson 2.13.4, they changed the primary annotation instrospector (the entity that inspect the annotations in use) from This was done because a new module for jakarta was added. And the problem is that we add dynamically the Line 92 in 9bc683f
Therefore, the new behaviour in |
I always forget that they based the JAX-RS JSON support in Jackson on the XML one... |
@Sgitario are you sure it was only Trying to make sure I understand why the behavior change. Because I would have expected Jackson 2.13 non-jakarta to have a javax equivalent of this. |
Actually, before it was working because |
@Sgitario so https://github.com/FasterXML/jackson-modules-base/blob/2.13/jaxb/src/main/java/com/fasterxml/jackson/module/jaxb/JaxbAnnotationIntrospector.java is not used in the javax flavor? From what I read from the Jackson commit, we need to explicitly register the module. So was the JAXB module not registered before? And now the JakartaXmlBind one is? |
The |
@Sgitario can you point me where it's done? Because that's not obvious to me that it should. |
The
extensions/panache/hibernate-orm-rest-data-panache/deployment
tests injakarta-rewrite
has started to fail (not every time AFAICS) with stackoverflow errors:I always get the error in
io.quarkus.hibernate.orm.rest.data.panache.deployment.entity.PanacheEntityResourcePathCustomisationTest
locally. It seems the other tests are OK.We have some Jackson annotations to prevent this issue so not sure what's going on. And also not sure what's specific to Jakarta.
What I don't understand is that it's not an issue in main Quarkus. Also once we have this error, Quarkus is in a very weird state as once I reproduce this, the build is stuck for several minutes until it's cancelled by our test infrastructure.
The text was updated successfully, but these errors were encountered: