Graham,
On 11/28/23 14:11, Graham Leggett wrote:
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.
Might I recommend a more modest upgrade first, like to Java 11? I know
it seems like a "bad thing" (Java 17 is more better, and if we are gonna
move, let's move to the latest... uh, okay next-to-latest) but you may
find that fewer things break at once and you can fix those fewer things
more easily than if you break 10 things at once and have a harder time
figuring out which things are broken for which reasons and not for other
reasons which are breaking other things :)
(At $work, we recently had 3 semi-unrelated enhancement requests and the
testers kept re-opening ALL THREE any time one of them had an issue
because, workflow-wise, there was overlap. So if one of them was broken
because of (A), they would re-open all 3 of them even though it was only
(A) broken and affecting those other things. I finally had to stop
claiming that more than one was RESOLVED at a time because the (digital)
paperwork was driving me mad.)
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
