Torsten Curdt wrote:
IMHO having map:act *and* map:call is not really nice.

Why not? IMHO it is more readable to have

  <map:act function="foo"/>
  <map:call function="bar"/>

than:

  <map:call action="my-action" function="function-name"/>
  <map:call flow="my-flow" function="start-of-flow"/>

I'd rather rename <map:call/> to something more flow-specific (e.g. <map:invoke/>) than <map:act/> to <map:call/>.

Another reason for clear separation of these two concepts is that <map:call function=""/> requires to sendPage(), while action does not.

Vadim

Reply via email to