After further investigations it seems like exceptions
are passed to the error handler inside the treeprocessor.
But requests using the cocoon protcol don't go through
the treeprocessor the same way as external ones.
So basically error handling is missing - or broken for
such internal requests.

I think this is a vital feature and I am
wondering why noone hit that before.

What do you guys think?

Mr. Treeprocessor (Sylvain) and
Mr. Pipeline (Carsten) in particular ;-)

cheers
--
Torsten

Reply via email to