Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: domain of wheleph@gmail.com designates
 209.85.216.45 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4E428BD9.30606@christopherschultz.net>
References: 
 <CAFaTLCBgacZEvPAsqd=2-xF7n9bwcUORbMaHgMbe-z1GZ=WWVg@mail.gmail.com>
 <4E419A2E.70404@apache.org> <4E428BD9.30606@christopherschultz.net>
From: Volodymyr Sobotovich <wheleph@gmail.com>
Date: Fri, 12 Aug 2011 09:04:45 +0300
Message-ID: 
 <CAFaTLCA0PYFsZoh6j7z78Hoz8i8CbNjym+ED5GgarbuJnWZ16w@mail.gmail.com>
Subject: Re: ServletRequestListener.requestDestroyed is called before request
 leaves a webapp
To: Tomcat Developers List <dev@tomcat.apache.org>
Content-Type: text/plain; charset=UTF-8

I submitted BUG51653
(https://issues.apache.org/bugzilla/show_bug.cgi?id=51653) for this
issue.

On Wed, Aug 10, 2011 at 4:47 PM, Christopher Schultz
<chris@christopherschultz.net> wrote:
> Mark,
>
> On 8/9/2011 4:35 PM, Mark Thomas wrote:
>> Addressing this would mean either:
>> a) moving the error handling to the context (inside the calls to the
>> ServletRequestListener) or
>
> +1
>
> This just feels like the right state management level to me. Certainly
> the default error handler can be called just as easily from this level
> of the code.
>
> -chris
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org