Am 30.06.2022 um 06:18 schrieb Greg Wilkins:
You can use a GlobalWebappConfigBinding in the deployer to apply an XML file to
every deployed context. This should allow you to get the error page and then set
the no stack field.
Thanks for mentioning all the options and I've used yours to get this done.
I'm not sure if my actual implementation is suitable as general example,
though ;-) because instead of providing an XML I've overwritten
GlobalWebappConfigBinding's to access the error handlers directly:
public void processBinding(Node arg0, App arg1) throws Exception {
ContextHandler ch = arg1.getContextHandler();
ErrorHandler eh = ch.getErrorHandler();
eh.setShowStacks(false);
eh.setShowServlet(false);
}
I thought we had some doco/examples, but I'm struggling to find them.
That's a problem, yes. When I search for something I often end up
at an article on wiki.eclipse.org that always starts with
"THIS IS NOT THE DOCUMENTATION YOU ARE LOOKING FOR!!!!!" with the
generic link to the Jetty Documentation Hub.
While my imminent problem is solved, I'd look forward to some example
to see how it's done "correctly" and given the number of similar
questions on Stack Overflow this should make others happy as well.
Thanks and cheers, Lothar
_______________________________________________
jetty-users mailing list
jetty-users@eclipse.org
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jetty-users
