jsr372-experts@javaserverfaces-spec-public.java.net

[jsr372-experts] Re: UICommand#decode() ordering of client behavior events and action event not consistent in Mojarra and MyFaces

From: Bauke Scholtz <balusc_at_gmail.com>
Date: Fri, 6 Mar 2015 17:46:11 +0100

Indeed, exactly as how actionListener/action work right now.

Cheers, B

On Fri, Mar 6, 2015 at 5:11 PM, arjan tijms <arjan.tijms_at_gmail.com> wrote:

> Hi,
>
> I'd say the general expectation is that listeners are always invoked
> first, and the action is the final thing called.
>
> Kind regards,
> Arjan
>
>
>
> On Fri, Mar 6, 2015 at 4:29 PM, Bauke Scholtz <balusc_at_gmail.com> wrote:
> > Hi,
> >
> > Trigger:
> > http://stackoverflow.com/q/28901284
> >
> > Code:
> > <h:commandLink action="#{bean.action}">
> > <f:ajax listener="#{bean.listener}" />
> > </h:commandLink>
> >
> > Mojarra:
> > Listener is first invoked and then action.
> >
> > MyFaces:
> > Action is first invoked and then listener.
> >
> > Who's correct? I couldn't find this in the spec. We need to align out
> it. As
> > the action is supposed to be definitive (because of the navigation case
> > outcome), I find Mojarra behavior is correct.
> >
> > Cheers, B
>