The JAXB API classes were added to runwar around the time Java 11 came out as an attempt to shim the missing classes in the JRE. I believe this was before the CF engines officially supported java 11.
The existence of these classes is causing issues with Lucee's Hibernate extension. The extension bundles its own JAXB API, but the classes in runwar are being used instead which cannot "find" the implementation jar (inside an OSGI bundle).
I question if this jar is really necessary in CommandBox as I think most libraries using JAXB have already moved to bundle the API themselves. I don't know if it will break anything, but let's try removing it.
Activity
Show:
Brad WoodDecember 29, 2022 at 8:17 PM
Based on initial tests, this seems to work.
Fixed
Pinned fields
Click on the next to a field label to start pinning.
The JAXB API classes were added to runwar around the time Java 11 came out as an attempt to shim the missing classes in the JRE. I believe this was before the CF engines officially supported java 11.
The existence of these classes is causing issues with Lucee's Hibernate extension. The extension bundles its own JAXB API, but the classes in runwar are being used instead which cannot "find" the implementation jar (inside an OSGI bundle).
I question if this jar is really necessary in CommandBox as I think most libraries using JAXB have already moved to bundle the API themselves. I don't know if it will break anything, but let's try removing it.