|
|
This message has originated from an
External Source. Please use proper judgment and caution when opening attachments, clicking links, or responding to this email. For any questions don't hesitate to reach out to security@xxxxxxxxx
|
There is a fallback from a context error handler to the server error handler. However, I see that the EE8 start is always setting an error handler if one is not already set. You can
just set the same error handler on both the server and context (although I do see an issue with stop/start cycles).
Experiment with this approach and then open an issue with any problems you encounter.
I’m migrating from Jetty 9 to 12.1 and had a question about the intended ErrorHandler behavior. I have a custom handler that I want to be used for all contexts (and no context) on the server, and I’m trying to avoid having 2 different implementations of it
for the server and my EE8 applications. Is there supposed to be some sort of fallback behavior wherein if a context does not have an ErrorHandler set it falls back to the server level one? The code in ErrorHandler.getErrorHandler() looks like it tries to
do this but I couldn’t get it to work. Thanks!
--
