That doesn't actually prevent the back button returning to the form. What id does do, however, is when the user submits the form, it throws an org.apache.cocoon.components.flow.InvalidContinuationException:
Right. If you want to block completely the usage of the back button, you'll have to play with client-side caching and browser differences and the like. There was a thread on this issue some time ago on this list, but I didn't follow it since I don't think it's worth the hassle.
I can't seem to catch this in the flowscript. Is there a way to catch it in the sitemap? I thought about a map:error-handler, but reading the documentation, it only seems to handle HTTP status codes - not cocoon excpetions.
It's right there in the main sitemap of the sample webapp:
<map:handle-errors>
<map:select type="exception">...
<map:when test="invalid-continuation">
<map:generate type="notifying"/>
<map:transform src="stylesheets/system/error2html.xslt">
<map:parameter name="contextPath" value="{request:contextPath}"/>
<map:parameter name="pageTitle" value="Invalid Continuation"/>
</map:transform>
<map:serialize status-code="404"/>
</map:when>
Ugo
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
