Sure, how about (inspired from the main sitemap):
<map:selector logger="sitemap.selector.exception" name="exception" src="org.apache.cocoon.selection.ExceptionSelector">
<exception class="org.apache.cocoon.components.flow.InvalidContinuationException" name="invalid-continuation"/>
<!-- The statement below tells the selector to unroll as much exceptions as possible -->
<exception class="java.lang.Throwable" unroll="true"/>
</map:selector>
...
<map:pipeline>
...
<map:handle-errors>
<map:select type="exception">
<map:when test="invalid-continuation">
<map:read src="timeout.html"/>
</map:when>
</map:select>
</map:handle-errors>
</map:pipeline>
beyaRecords wrote:
How to best deal with this? i know why it is being caused. I just don't want my clients seeing that horrible error page. Is there no way I can, soften the situation, by placing a pipe in my sitemap which checks for this problem and then redirects the user to to a particular page of my choice??
regards
Uzo
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
