Let's use this as an example of a possible action:
<map:act name="session-validate">
.. do something ..
</map:act>
Now, what do you do if you want to action fails, yet you still want to
modify the pipeline based on that failed action? Well, of course, you
could always write the action as a selector. But what if you want to
reuse some code already written as an action? You could of course write
a wrapper selector, but I don't see why that should be necessary. Why
not something along these lines::
<map:act name="session-validate">
<map:act-successful>
.. do something ..
</map:act-success>
<map:act-failure>
.. do something else ..
</map:act-failure>
</map:act>
Is there a good reason for not doing things this way that I am missing
(or maybe a way of doing this that I have yet to discover)? I would
assume you could do something similar for action sets.
Thanks!
Bryan
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
