Closed FernandoFranzini closed 1 year ago
As far as I can see, this conflict does not seem to be with Spring API specifically but rather with Hibernate's Jackson integration which relies on the presence of a StAX provider (a javax.xml.stream.XMLInputFactory
). I'm not aware of any Payara specifics there, that StAX setup usually comes with the JDK itself.
In any case, I'd expect this to fail for any Hibernate bootstrap attempt, within or outside of Spring. You might have to tweak Hibernate's configuration to not activate its Jackson integration, or configure Payara to expose a common StAX provider.
When I switched from hibernate 6 to 5, it worked
<dependency>
<groupId>org.hibernate.orm</groupId>
<artifactId>hibernate-core</artifactId>
<version>6.1.6.Final</version>
</dependency>
<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate-core-jakarta</artifactId>
<version>5.6.14.Final</version>
</dependency>
Does this mean that there is a problem in hibernate 6x? Regards
Looks like Hibernate 6 has some different Jackson integration there, so it might indeed be Hibernate 6 specific. In any case, I would expect the default Jackson integration to be configurable on Hibernate's side, turning it off completely or at least turning off the Jackson XML part of it.
I'm afraid that just like #29718, this is not an actual problem to be solved on Spring's own side, as far as I can see. This needs to be taken to Hibernate and Payara. If there is anything concrete we can do from our side (based on feedback from Hibernate and/or Payara), let us know.
Hello Springers
Need help. My spring app runs correctly in the TDD staging environment. But when I run it inside payara application server, an error is generated:
It seems to me that Payara's Jackson provider overlaps or conflicts with some Spring API. Any suggestions on how to resolve? Regards