--- Sylvain Wallez [EMAIL PROTECTED] wrote:
Error-handlers are not invoked on internal requests, which is what the
flow uses behind sendPage[AndWait](). In that case, the exception are
propagated.
How do you catch these exceptions in a flowscript? I tried a simple
Sylvain Wallez wrote:
The flow uses an internal redirect to handle an external request. This
means that the propagated exception is only catched by the top-level
Cocoon object which outputs the default error page (if configured to
do so). So we can say that the behaviour of not executing error
Sylvain Wallez wrote:
There are 2 solutions to solve this :
1/ apply the same policy for internal redirects than the one that
was active before the redirect (i.e. handle errors on internal
redirects resulting from external requests)
This totally makes sense.
2/ let the user choose the
