i think the problem here is that all exceptions are propagated, but not all are caught by the handle:errors section.
It would be good to get a statement from an expert here on exactly what exception to throw so they are guaranteed to be caught by the handle:error.
You can make any exception you wish. The trick is to use the ExceptionSelector and tell it about your custom Exception:
Taken from the main default sitemap.xmap in Cocoon:
<!--+
| Exception selector : used in <map:handle> errors to build different pipelines
| depending on the error that occured.
| The configuration allows to associate a symbolic name to exception classes
| which is used in the <map:when> tests.
| An exception can also be "unrolled", meaning that cascaded exception will be checked.
+-->
<map:selector logger="sitemap.selector.exception" name="exception" src="org.apache.cocoon.selection.ExceptionSelector">
<exception class="org.apache.cocoon.ResourceNotFoundException" name="not-found"/>
<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>
HTH,
Tony
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
