Hello Graham, > -----Ursprüngliche Nachricht----- > Von: Graham Leggett <minf...@sharp.fm.INVALID> > Gesendet: Dienstag, 28. November 2023 20:12 > An: Tomcat Users List <users@tomcat.apache.org> > Betreff: Re: 400 Bad Request - where do I find the detailed reason for the > bad request so I can fix it? > > On 28 Nov 2023, at 18:42, Christopher Schultz <ch...@christopherschultz.net> > wrote: > > > In your debugger, when you break-on-exception, what happens if you > allow the exception to propagate up to the first exception-handler? Does > Tomcat swallow the exception? Or it it caught elsewhere? > > The exception eventually ends up inside ErrorReportValve, but I’m > debugging a remote box and don’t have any of the source code tied up - will > do further digging. > > > When you say you have an "unmarshalling problem"... do you mean in your > own application? Or something in Tomcat? (I can't think of anything in Tomcat > we'd call "unmarshalling", but I figure I'd ask.) > > I’m in dependency hell - java8 to java17, JAXB as used by Jersey2 broke. No > idea why, but an internal Oracle implementation is hardcoded somewhere. > > java.lang.ClassNotFoundException: oracle.xml.jaxp.JXSAXParserFactory
I think you got trapped in the javax-jakarta hell after upgrading. As a general recommendation, you should upgrade all libraries in your app. Mostly all new versions have switched to using Jakarta. Do you use and build system like gradle or maven? They should take care of the new dependencies. Otherwise you have to look it up. If some libraries don’t support Jakarta package yet, you have to add the legacy jaxb libs: https://mvnrepository.com/artifact/com.sun.xml.bind/jaxb-impl > Regards, > Graham > —
