I agree with Carsten. The output should be flushed to the real output stream only after the sitemap processing has ended.
Allowing direct access to the output stream proved to be very problematic for JSP applications as well. The 2.3 filters were warmly welcomed in the JSP world. The one big issue is the size of the buffer. However I was never really worried too much about it, because web applications are usually not ftp servers. Especially Cocoon applications. Ivelin ----- Original Message ----- From: "Carsten Ziegeler" <[EMAIL PROTECTED]> To: "Cocoon-Dev" <[EMAIL PROTECTED]> Sent: Wednesday, September 11, 2002 6:05 AM Subject: Error Handling is NOT working > 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 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
