On 11/16/05, Simon Kitching <[EMAIL PROTECTED]> wrote: > AFAIK in > practice only one such component will actually cause an ActionEvent on > the server side. Actually, for links there is is a single hidden field > in the form that is assigned the id of the link actually clicked, so > it's physically impossible for more than one link component to fire its > action.
While it's true that only one UICommand "action" attribute will be queued, there can be any number of other kinds of actionListeners, valueChangeListeners, updateActionListeners, MyCustomListeners, and so on, that will also be queued as action events, all of which will be executed before the "action" attribute. But like I said above, maybe I'm just misunderstanding the question.
