|
Assuming a pipeline as in the example
below:
<map:match pattern="testDelete.html"> <map:generate type="request"/> <map:transform src="" type="xslt"/> <map:act
type="action1">...</map:act>
<map:transform src="" type="xslt"/> <map:act
type="action2">...</map:act>
...
<map:transform src="" type="xslt"/> <map:act
type="actionN">...</map:act>
<map:serialize type="html"/> </map:match> Is there a straightforward way to implement some sort of "On Error"
clause in the pipeline above, so that if there is any
specific condition
set by any of the actions, the subsequent actions/transformers
are simply bypassed and a final action/transformer is executed?
I understand Cocoon has a "handles-errors" tag that handles
certain types of pipeline errors (a requested pipeline is not found,
a stylesheet is missing, a resource is not found, etc...).
These have to do with mistakes in the configuration of the pipeline.
But I am considering application-specific conditions, for which the
"handles-errors" does not seem to be appropriate.
I guess I could add lots of selectors to the example above, but
one could easily imagine how cluttered it would become.
Any ideas?
Thanks,
jlerm
|
