Maybe I did not explain clearly what I meant.
SAX processing is extremely valuable and it should not be compromised. And in fact it does not have to be. Here is a simple suggestion. What if we wrap the Cocoon servlet with another filter servlet? This way the J2EE container (Servlets 2.3 compatible) will take care of passing a secondary output stream to Cocoon. Since it is just a dynamically expandable ByteArrayStream, it can be flushed at any point. Ivelin ----- Original Message ----- From: "Torsten Curdt" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, September 11, 2002 8:56 AM Subject: Re: Error Handling is NOT working <snip/> Guys, isn't it obvious we cannot realy provide errors in a user friendly manner since we are delivering the page on-the-fly via SAX? Buffering the whole page seems to reduce the positve aspects we get from using SAX and we get closer to Cocoon1. Maybe we should have two different modes to run cocoon or at least pipelines in: buffered and unbuffered. So one could use e.g. buffered for development und unbuffered for deployment?! With unbuffered we will always have the problem that after the first generated SAX event we cannot really make sure we are able to present an error page to the user... Or did I miss here something? Sorry, I haven't followed the thread very closely up to now... -- Torsten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
