On Sat, 11 Aug 2012 09:07:11 +0100
Mark Thomas wrote:
>
> You are already in an error page so sendError will not trigger the
> error page matching process again. If it did there is a strong
> possibility that you could end up in an infinite loop.
>
> Mark
>
This makes sense, thanks!
On 11/08/2012 08:17, Vladimir Mokrozub wrote:
>> On Fri, 10 Aug 2012 10:50:17 -0400
>> Christopher Schultz wrote:
>
>>>
>>> When I try to send error page directly from ErrorHandler using
>>> HttpServletResponse, it works fine and page is displayed, so it
>>> seems the problem is with sendError()
>On Fri, 10 Aug 2012 10:50:17 -0400
>Christopher Schultz wrote:
> >
> > When I try to send error page directly from ErrorHandler using
> > HttpServletResponse, it works fine and page is displayed, so it
> > seems the problem is with sendError() method. Is this an expected
> > behaviour or some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vlad,
On 8/10/12 3:48 AM, Vladimir Mokrozub wrote:
> And here is ErrorHandler servlet: -
> @WebServlet("/ErrorHandler") public class ErrorHandler extends
> HttpServlet { protected void doGet(HttpServletRequest request,
> HttpServ
Hello,
I have a problem (tried Tomcat 7.0.29 and Glassfish 3.1) with
displaying an error page when exception is thrown and processed by
another servlet.
Here is what I've added to web.xml:
-
java.lang.Throwable
/ErrorHandler
-
Here is a t
