Jon Iles

Hello! I've had a look at this and it appears that a workable solution is to update MPXJ to use JAXB 3. This will maintain compatibility with Java 1.8, and...

I've had a bit of a rethink on this one. Updating to JAXB3 is a fairly big upheaval at the moment, with the potential to break code unexpectedly for existing...

> If I understood your comment correctly, you acknowledged that it does not work with Spring Boot 3 and JAXB3? So it does not solve the problem for me. The...

@stophi-dev I may have a way forward with this. In my local testing I've updated MPXJ to use the `javax.xml` and `com.sun.xml` versions of the JAXB 2 packages rather than...

The change I've just made to switch MPXJ to use `javax.xml.bind:jaxb-api` and `com.sun.xml.bind:jaxb-impl` ensures that MPXJ is using dependencies with completely different Maven coordinates than the current Jakarta JAXB 3...

Hello! Sorry it's taken a while, but the change to move to JAXB3 (https://github.com/joniles/mpxj/pull/561) has now been merged and will form part of the 13.0.0 release.