cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Søren Krum <>
Subject Re: Blocks and error handling
Date Wed, 03 Jun 2009 11:55:08 GMT

thanks for the suggestion, I was afraid that such a solution would 
come... :-)

My original error handling does something like this:

        <map:select type="exception">
          <map:when test="not-found">
          <map:when test="premature">
          <map:when test="citrix-overload">

So it would be interesting that the error / the exception survive, or is there a quick way
to change the route of processing in a pipeline taking  the already produced content into
account? Then i could take the class attribute from the exception-report.

Looks like i have to mess up all my sitemaps :-(

Best Regards



To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message