Carsten Ziegeler wrote:
> Hi,
>
> I just have to repeat an email I wrote over a year ago, because the
> problem is getting worse:
>
> If an error occurs in the pipeline, the error handler is called and
> produces some output (or a response). At this time, the original
> pipeline could have already output some information and you might
> get an "response already committed" exception or something like that.
>
> Ok, so far so good, but since some time a serializer flushed the output
> stream when it is recycled...so the response is always already committed
> and the output stream can't be reset - and when the error handler trys
> to create its output, an exception is thrown!
>
> If we want to keep this error handler stuff I still vote for an
> intermediate output stream for the normal pipeline. This output stream
> "is copied" to the real output stream only if no error occurs.
> This is some extra performance cost - so we could make this somewhere
> configurable.
>
> If anyone has a different solution, I'm all ears - but the current
> implementation is absolutely useless.
Carsten, do what you want, I'm really fed up with error handling.
I'll start to complain myself now, let's see if it helps.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
