Simple question:
Do we allow actions to wrap call functions in the sitemap?
Yes. Moreover, map:call is subject to general sitemap syntax rules. E.g., it can be nested within act, select, match tags and can not appear after serialize, read, redirect.
<map:match pattern="xxx"> <map:act type="myAction"> <map:call function="myFunction"/> </map:act> </map:match>
Are there any reasons that make this useful?
Is there a reason to disable this?
PS Don't forget that match is no special tag; it can be omitted (as everything else):
<map:pipeline>
<map:act type="myAction">
<map:call function="myFunction"/>
</map:act>
</map:pipeline>Or:
<map:pipeline> <map:call function="myFunction"/> </map:pipeline>
Vadim
Maybe with the authentication framework? I think it is also possible to work around it with redirects if we don't allow this.
What do you think?
Reinhard
