I do know about debugging and hash codes :), following the Jetty docs i need to set a ErrorHandler on the Server context:
If no error page mapping is defined, or if the error page resource itself has an error, then the error page will be generated by an instance of ErrorHandler configured either the Context or the Server. How and where to set my ErrorPage on the Context, as the Server has the bean already set... Am Dienstag, 6. Februar 2018 12:06:45 UTC+1 schrieb Grzegorz Grzybek: > > > > 2018-02-06 11:58 GMT+01:00 Maurice Betzel <[email protected] > <javascript:>>: > >> I have added my own error handler with addBean and i can see it on the >> Server object, but in the Jetty Response object on method sendError the >> ErrorHandler.getErrorHandler returns the Jetty ErrorPageErrorHandler. I am >> missing something more... >> > > Another debugging hint then - I usually try to not hashCodes of objects > (System.identityHashCode(object)) for different objects and check if later > these are the same objects. So I'd put a breakpoint where <Add ... > ErrorHandler> is called and then verify if it's the same issue at > invocation time. > > regards > Grzegorz > >> -- >> -- >> ------------------ >> OPS4J - http://www.ops4j.org - [email protected] <javascript:> >> >> --- >> You received this message because you are subscribed to the Google Groups >> "OPS4J" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- -- ------------------ OPS4J - http://www.ops4j.org - [email protected] --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
