and that feels like replacing one evil with
another
* use the package-accepting variant of `JAXBContext::newInstance` that
also takes a class loader and pass the correct loader, although that
requires some refactoring
so long ... Nicolai
On 26.07.2018 12:41, Nicolai Parlog wrote:
> Hi!
>
&
Hi Christopher,
unfortunately that didn't change the observable behavior - exact same
error message as when the JARs were in the application's lib folder.
so long ... Nicolai
On 26.07.2018 17:37, Christopher Schultz wrote:
> Nicolai,
>
> On 7/26/18 6:41 AM, Nicolai Parlog wro
Hi!
TL;DR: On Java 10.0.1, a web app in Tomcat 9.0.8.0 has no access to JAXB
even though its reference implementation is present on the class path.
(This looks like a bug to me, but "Before you report a bug" urged me to
ask here first. :) )
NOTE: I already asked [on
